Skip to content
This repository has been archived by the owner on Apr 10, 2024. It is now read-only.

Successful runs on an integration branch should prune merged branches #3

Open
asmith-mdsol opened this issue Nov 1, 2012 · 3 comments

Comments

@asmith-mdsol
Copy link
Contributor

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.

@asmith-mdsol
Copy link
Contributor Author

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).

@cross311
Copy link

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.

@asmith-mdsol
Copy link
Contributor Author

I think we'd make this opt-in and configurable if we added this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants