Sometimes, I'll merge a feature/bug branch into master and forget to delete it. Or, I'll push a branch to GitHub and submit a Pull Request.
It may be convenient if there was some sort of algorithm to detect "abandoned" branches.
popular branch = branch with frequent commits/merges (e.g. master)
important branch = branch with many commits/merges, but may not receive frequent commits/merges anymore (e.g. v2.34)
Signs of an "abandoned" branch:
[ ] merged into a popular/important branch AND hasn't had a commit in TimeSpan
[ ] merged into another branch which neither have had a commit in TimeSpan
[ ] pushed to remote for a Pull Request (which gets accepted) and hasn't had a commit in TimeSpan
Popular
[ ] frequency of commits
[ ] number of commmits
[ ] number of merges
Important
[ ] number of commits
[ ] number of merges
[ ] frequency of commits/merges (before being forgotten)
Indicators should probably be normalized to accommodate repositories which haven't been recently used.
Sometimes, I'll merge a feature/bug branch into master and forget to delete it. Or, I'll push a branch to GitHub and submit a Pull Request.
It may be convenient if there was some sort of algorithm to detect "abandoned" branches.
popular branch = branch with frequent commits/merges (e.g. master) important branch = branch with many commits/merges, but may not receive frequent commits/merges anymore (e.g. v2.34)
Signs of an "abandoned" branch:
Popular
Important
Indicators should probably be normalized to accommodate repositories which haven't been recently used.