search

statistikat / simPop

Simulation of Synthetic Populations for Survey Data Considering Auxiliary Information
30 stars 7 forks source link

MAINT: drop stale branches #32

Open vkhodygo opened 8 months ago

vkhodygo commented 8 months ago

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 commented 8 months ago

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 commented 8 months ago

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 commented 8 months ago

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