Skip to content
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

Open
vkhodygo opened this issue Jan 31, 2024 · 3 comments
Open

MAINT: drop stale branches #32

vkhodygo opened this issue Jan 31, 2024 · 3 comments

Comments

@vkhodygo
Copy link

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.

@matthias-da
Copy link
Collaborator

Thank you very much for this hint. I suggest that everyone who has created branches evaluates their branch.
My impression is that almost all branches can be deleted, thus I will do this, except @alexkowa @bernhard-da @GregorDeCillia would like to make pull requests from any of the branches.
If I do not hear from you, I will start to delete them except the only one which is active.
Thanks for checking.

@alexkowa
Copy link
Member

alexkowa commented Feb 1, 2024

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.

@vkhodygo
Copy link
Author

vkhodygo commented Feb 2, 2024

@alexkowa It creates clutter that's difficult to manage unless your workflow is designed for this.

I mean some of them are merged and implement a certain functionality or method, fix a certain issue

Regarding history, you can easily recreate a branch that's been merged and deleted, that's how git works.

some come from a special project where the package is used

The changes that are not in the main/master should be reviewed on case-by-case basis. For the rest, isn't it easier to replace a separate branch with a tag?

Anyway, that's just a strong suggestion, the rest is up to you.

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

No branches or pull requests

3 participants