code-423n4 / code-423n4/code423n4.com
Automate clean up of warden registration branches
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 179
- Forks
- 173
- PR merge metrics
- No merged PRs in 30d
Description
Problem / opportunity:
There currently is no clear retention policy on warden registration PR branches. When closed, the branches aren't always deleted, leaving an excessive number of branches remaining in git history.
Desired outcome
Branches for closed PR's are automatically deleted after 30days.
Solution
Add a github action to automatically clean up PR branches that have been closed after 30 days.
Additional context
Github PR branch retention period is currently indefinite, so branches can be manually deleted on closed PR's right away. We shouldn't rely on a human needing to do this though. 30days is probably excessive, in reality this could probably be immediate, but we do need to bulk remove the older branches if we did this as a PR closed action.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the repository's existing GitHub Actions configuration and the GitHub API support for identifying closed PR branches older than 30 days. Done means an automated workflow removes only eligible branches according to the stated 30-day policy, with its behavior verified against representative closed pull requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100