[FOLIO-3346] SPIKE: Prune stale git branches in github.com/folio-org (policy) Created: 17/Nov/21 Updated: 10/May/23 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | John Malconian | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | DevOps Sprint 160 |
| Development Team: | FOLIO DevOps |
| Description |
|
Many years of FOLIO development and a few hundred repos have resulted in lots of stale or abandoned branches, PRs, and existing branches that have been merged but not deleted. These should be cleaned up. This also impacts the performance and storage capacity on the Jenkins server. We should also develop a policy that dictates and enforces the maximum length of time an PR will remain open before it is automatically closed and stale branches deleted. |
| Comments |
| Comment by David Crossley [ 24/May/22 ] |
|
There is some encouragement to developers: https://dev.folio.org/guides/tidy-repository/ |
| Comment by Jakub Skoczen [ 08/Aug/22 ] |
|
Jakub Skoczen ask that this a policy regarding this is in the DoD. |