-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MAINT: drop stale branches #32
Comments
Thank you very much for this hint. I suggest that everyone who has created branches evaluates their branch. |
Sure. But is there a strong argument to remove them. I mean some of them are merged and implement a certain functionality or method, fix a certain issue, some come from a special project where the package is used, so it is kind of the history of the repo. |
@alexkowa It creates clutter that's difficult to manage unless your workflow is designed for this.
Regarding history, you can easily recreate a branch that's been merged and deleted, that's how
The changes that are not in the Anyway, that's just a strong suggestion, the rest is up to you. |
Hey Folks,
What do you think about the suggestion? There are branches that have been merged already and not needed anymore. There are also some that have dangling commits and could be merged as well or dropped altogether.
The text was updated successfully, but these errors were encountered: