-
-
Notifications
You must be signed in to change notification settings - Fork 630
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
Notify when labels are changed in issues or pull requests #16979
Comments
Perhaps put in an issue with GitHub accessibility, to request that labels
receive notification status? Therefore, if people are subscribed to issues,
labels will be notified on GitHub and by email, if they are setup for that.
|
Hi @XLTechie . Can you provide links to documentation about filling issues with GitHub Accessibility? Your idea seems reasonable, if I have understood it well. |
@nvdaes Perhaps start here: https://github.com/orgs/community/discussions/categories/accessibility |
Thanks @XLTechie . I've created this discussion: |
Apart of automatic notification, giving a reason is sometimes useful and not always done when needed. E.g. sometimes the blocked label is applied, but we do not always know why the issue / PR is being blocked. |
Closing this as won't fix. Comments would be too noisy on this repository. Please provide feedback to GitHub for a proper solution |
Is your feature request related to a problem? Please describe.
When someone works on issues/pull requests, this developer needs to know when labels are added or removed, for example, if the issue has been triaged or the pull request is locked waiting for testing or product decision.
Describe the solution you'd like
When labels are added or removed, a comment may be added so that followers of the issue can receive an email notification. For example: "Labels: triaged, p4, locked/needsTesting", etc.
Describe alternatives you've considered
Developers can check this manually from time to time.
Additional context
GitHub Actions may be used for this:
https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows
The text was updated successfully, but these errors were encountered: