You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 10, 2024. It is now read-only.
Using GitHub pull requests results in a large number of stale feature branches being left behind. CI runs should prune these merged branches automatically when appropriate.
The text was updated successfully, but these errors were encountered:
This is somewhat less useful now as GitHub supports delete branches in its UI but there may still be benefit in this for catching cases where people forget to do it themselves, or for those not using GitHub (or its UI).
I can see one danger in this: If you follow the git flow model the master branch is considered a merged branch. Also some teams use branches as their release tags, which would also be considered a merged branch.
Using GitHub pull requests results in a large number of stale feature branches being left behind. CI runs should prune these merged branches automatically when appropriate.
The text was updated successfully, but these errors were encountered: