-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Rework Labeling & Project Automation Workflows #32605
Conversation
Community NoteVoting for Prioritization
For Submitters
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀
Update Project Automation Workflows
Community NoteVoting for Prioritization
For Submitters
|
Hey @justinretzolk 👋 Thank you very much for your contribution! At times, our maintainers need to make direct edits to pull requests in order to help get it ready to be merged. Your current settings do not allow maintainers to make such edits. To help facilitate this, update your pull request to allow such edits as described in GitHub's Allowing changes to a pull request branch created from a fork documentation. (If you're using a fork owned by an organization, your organization may not allow you to change this setting. If that is the case, let us know.) |
This functionality has been released in v5.10.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
This PR updates our labeling workflows in preparation for the new Project board. Some key points of interest:
gh
CLI is used directly to add/remove labelsreuseable-add-or-remove-labels
workflow has been removed, as it's no longer neededneeds-triage
is now applied conditionally on issue/pr open, so has been removed from issue templatesissues.yml
andpull_request_target.yml
files respectively)Below are the labels that are applied on a given action:
needs-triage
to non-maintainer issues and PRs on openprioritized
to maintainer PRs on openpartner
to partner PRs on openexternal-maintainer
to external maintainer PRs on openprioritized
to issues when assigned to a maintainerstale
andwaiting-response
when non-maintainers comment on issues and PRsneeds-triage
andwaiting-response
when issues or PRs are closedprioritized
when an item is included in a releaseThis PR also adds workflows to:
Add items to the Project board
Note: Where Status field is marked as
n/a
below, the status isn't explicitly set. If the item is already in the Project, the Status will not be changed. If the workflow is adding the item to the Project, the Status will be set to To Do by the built in workflow.Issues
regression
orprioritized
engineering-initiative
Pull Requests
regression
orprioritized
engineering-initiative
Pull Request Reviews
Archive items from the Project board when
Issues
Pull Requests
After #32666