-
-
Notifications
You must be signed in to change notification settings - Fork 504
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Thank everyone when the release goes out automagically. #3726
Comments
Would like to give this a go! |
Alright! |
Looks like the existing action doesn't support either the PR opener or the PR name in the body. Might need to add those features before we can do this. |
Will be looking into this. Since the comment is added to the PR itself maybe the PR name is not required? Created a draft PR in the meanwhile. |
This issue is marked as stale due to no activity within 30 days. If no further activity is detected within 7 days, it will be unassigned. |
Automatically unassigned after 7 days of inactivity. |
ooooops, forgot about this 😅 Got a WIP PR for adding the |
Marked PR ready for review. Had to end up using my own fork of the GitHub action in order to use the new feature of author and title template variables. Please see PR for explanations |
* ci: add workflow file for release contribution notifier * Use own fork of github-release-commenter
@N/A: Your PR/Issue |
Summary
We'd like to notify everyone who contributed to a production release.
Why?
Although we sometimes do this ourselves manually, we don't always have the cycles to do it. It's nice to know when your changes go out!
Details
This could be a process that is run manually when the release is done, or potentially something that automatically happens as part of the release.
Wording should be something like "@your_id: Your PR [PR title ] is part of today's Human Essentials production release. Thank you very much for your contribution!"
Reference: https://github.com/marketplace/actions/release-commenter
Criteria for completion
The text was updated successfully, but these errors were encountered: