feat: notify maintainers of releases and issues #75
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kormide
force-pushed
the
notify-maintainers
branch
from
a09cb13 to
1db334d
Compare
This was referenced Nov 6, 2023
kormide
force-pushed
the
notify-maintainers
branch
6 times, most recently
from
ad812c3 to
14c2a98
Compare
kormide
force-pushed
the
notify-maintainers
branch
2 times, most recently
from
9e37581 to
9620c98
Compare
kormide
commented
Nov 7, 2023
kormide
force-pushed
the
notify-maintainers
branch
2 times, most recently
from
23ae414 to
7b2438a
Compare
cgrindel
approved these changes
Nov 7, 2023
kormide
force-pushed
the
notify-maintainers
branch
2 times, most recently
from
33f3fee to
f778dcf
Compare
kormide
force-pushed
the
notify-maintainers
branch
from
f778dcf to
72a1829
Compare
This was referenced Nov 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It's common for a new user's first publish to fail and they receive no notification. This happens when they use release automation and the release author is the github-actions bot, so we can't attribute the release event to a user with an email.
This improves the chances that someone will receive an email by emailing errors to everyone in the maintainers list in the bcr entry's metadata.json file. It also makes maintainers aware of releases by tagging them in the PR body.
Related to #59