DEV: lots of obsolete branches could be pruned
Open
Developers Discussion
- Dominant language
- Java
- Stars
- 2.4k
- Forks
- 940
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 160
Description
Any objections to removing the following categories:
1. Branches associated with a PR that has been merged into master
2. Branches associated with a PR that has been closed
3. Branches that have no activity within the past two years
4. Branches that have been obsoleted by other merged changes addressing the same issue
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by reviewing the repository's branches and associated pull requests against the four proposed categories. Done would require an agreed pruning policy and confirmation that the obsolete branches can be removed without affecting active work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- release
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100