-
-
Notifications
You must be signed in to change notification settings - Fork 847
Closed
Labels
Complexity: MediumFeature: Board/GitHub MaintenanceProject board maintenance that we have to do repeatedlyProject board maintenance that we have to do repeatedlyautomationfor manual github board maintenance actions that are going to be automatedfor manual github board maintenance actions that are going to be automatedrole: back end/devOpsTasks for back-end developersTasks for back-end developerssize: 2ptCan be done in 7-12 hoursCan be done in 7-12 hours
Milestone
Description
Overview
Our Project Board has too many cards on it, causing it to slow down, and we want to optimize it. For this issue, you will need to create a GitHub Action that removes PRs that are unmerged AND closed from the project board.
Action Items
- Familiarize yourself with HackforLA's GitHub Actions guide
- If you have not done so already, create a copy of your own project board to test on GitHub (See Tip 6)
- Create a personal access token for the GitHub Action (See Tip 7)
- This should be a new job under the "PR Trigger" workflow
- This job should trigger when a Pull Request is closed without merge
- Be careful not to remove Pull Requests that are still open (neither merged nor closed)
Checks
- Test in your local environment that it works
- If a pull request is on the project board in any column, and it gets closed without merging, remove it from the project board
Resources/Instructions
- See associated ER for this issue: ER from TLDL: GHA to remove unmerged, closed PRs off the project board #4232
- Never done GitHub actions? Start here!
- GitHub Complex Workflows doc
- GitHub Actions Workflow Directory
- Events that trigger workflows
- Workflow syntax for GitHub Actions
- actions/github-script
- GitHub RESTAPI
- Using nektos/act to test GitHub Actions locally
- Plus a dev-written guide
- Additional dev-written guide for testing with a Project Board
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Complexity: MediumFeature: Board/GitHub MaintenanceProject board maintenance that we have to do repeatedlyProject board maintenance that we have to do repeatedlyautomationfor manual github board maintenance actions that are going to be automatedfor manual github board maintenance actions that are going to be automatedrole: back end/devOpsTasks for back-end developersTasks for back-end developerssize: 2ptCan be done in 7-12 hoursCan be done in 7-12 hours
Type
Projects
Status
Done