-
-
Notifications
You must be signed in to change notification settings - Fork 845
Closed
Labels
Complexity: LargeFeature: Board/GitHub MaintenanceProject board maintenance that we have to do repeatedlyProject board maintenance that we have to do repeatedlyLang: GHAGitHub ActionsGitHub Actionsrole: back end/devOpsTasks for back-end developersTasks for back-end developerssize: 5ptCan be done in 19-30 hoursCan be done in 19-30 hours
Milestone
Description
Overview
We need a new GitHub Action to detect when an assigned issue is closed without either a linked pull request (PR), an Ignore label, or a non-PR contribution label so that these issues are not lost.
Action Items
- Create a label:
non-PR contribution- Description: "For wiki additions/revisions, audit spreadsheet contributions, issue-making ERs and Epics, etc."
- Create a new GitHub Action with the following features
- Reopen issues that are closed without:
- A linked PR,
- An
Ignorelabel, OR - A
non-PR contributionlabel
- The automation should add the label:
ready for product - The automation should leave a comment on the issue with this text
This issue was reopened because it did not have any of the following: - A linked PR, - An `Ignore` label - A `non-PR contribution` label - The automation should move the issue to the "Questions / In Review" column on the project board
- Reopen issues that are closed without:
Resources/Instructions
Never done GitHub actions? Start here!
Hack for LA's Github Actions (latest)
Note that you might want to do something outside the scope of the above pseudo-code. If so, be sure to leave comments in your PR or this issue that justify your reasoning. If you feel you need guidance, be sure to reach out! We cannot foresee whether this issue is solvable, or what hard decisions have to be made, but we would love to hear and help you!
Additional resources:
Events that trigger workflows
Workflow syntax for GitHub Actions
GitHub GraphQL
Related Issues
This issue was initiated by ER #6291
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Complexity: LargeFeature: Board/GitHub MaintenanceProject board maintenance that we have to do repeatedlyProject board maintenance that we have to do repeatedlyLang: GHAGitHub ActionsGitHub Actionsrole: back end/devOpsTasks for back-end developersTasks for back-end developerssize: 5ptCan be done in 19-30 hoursCan be done in 19-30 hours
Type
Projects
Status
Done