Every day I come closer to writing a “branch eater” Github action that just deletes branches older than ~2 weeks.
If it has passed out of your current mental context and requires merge conflict resolution, it’s a liability. Write it again.
6 comments
Comments are closed.
@avdi an alternative is possibly something that deletes all of your calendar appointments for the next 24 hours once a branch hits a certain age threshold
@avdi There are plenty such actions in the marketplace, e.g. https://github.com/marketplace/actions/stale-branches
@avdi *me coming back from vacation wondering where my branch is* ☠️☠️
@avdi call it Red Deer?
@avdi If I have an old branch like that, I tag it with something like "exp-useful-name" and delete the branch. "exp" tells me that this was some experiment. That way the code is still in the repo in case I want to recall how I tried something.
@avdi
Except for code review work, like in Bitbucket, there's little value to stale branches.
And if it's needed, the author should be able to rebase and push again, with hardly any effort.