Cleanup stale release branches?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 20.6k
- Forks
- 3.3k
- PR merge metrics
- PR metrics pending
Description
Finding the active release branch can be a pain due the abundance of stale branches which, for whatever reason, tend to be sorted first in GitHub's UI:
Are these branches still beneficial to keep around?
For comparison, CPython is in the habit of deleting maintenance once the associated version falls out of support. This makes finding relevant branches in the UI comparatively easier: https://github.com/python/cpython/branches
Contributor guide
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
Review the repository's release branches and compare them with the supported release versions described in the issue. Determine which branches remain necessary and define what cleanup would be appropriate; the issue is done when the branch-retention decision is agreed and the stale branches are handled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100