chore: add issue reprioritization action#19758
Conversation
|
|
rix0rrr
left a comment
There was a problem hiding this comment.
I would find a different term for "graduation" here. That word has been overloaded with other activities we perform, and is confusing me.
skips graduation on any issue labeled no-graduation.
The 0-touch solution would be: don't do reprioritization if we've already reprioritized it once before. The only reason why it would be at a lower level then is because someone manually downprioritized it again (in which case that's a strong enough signal that The Machine should shut up and not do it again).
|
3 updates since the last review:
the no-touch solution is not in this PR but in the action itself. Adds a "unique" metadata to the message like |
|
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
|
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Add an issue graduation action with the following configuration: - run once a week on Sunday - finds `p2` issues and graduates them to `p1` if there are 20+ reactions - on every graduated issue, provides an automated message: "This issue has received a significant amount of attention so we are automatically upgrading its priority. A member of the community will see the re-prioritization and provide an update on the issue." See the action [here](https://github.com/kaizen3031593/issue-graduation-manager). ---- ### All Submissions: * [x] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/master/CONTRIBUTING.md) ### Adding new Unconventional Dependencies: * [ ] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/master/CONTRIBUTING.md/#adding-new-unconventional-dependencies) ### New Features * [ ] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/master/INTEGRATION_TESTS.md)? * [ ] Did you use `cdk-integ` to deploy the infrastructure and generate the snapshot (i.e. `cdk-integ` without `--dry-run`)? *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Add an issue graduation action with the following configuration:
p2issues and graduates them top1if there are 20+ reactionsSee the action here.
All Submissions:
Adding new Unconventional Dependencies:
New Features
cdk-integto deploy the infrastructure and generate the snapshot (i.e.cdk-integwithout--dry-run)?By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license