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

Delete stale branches #285

Open
stv0g opened this issue Apr 24, 2024 · 7 comments
Open

Delete stale branches #285

stv0g opened this issue Apr 24, 2024 · 7 comments

Comments

@stv0g
Copy link
Contributor

stv0g commented Apr 24, 2024

The DPsim repo on GitHub has currently quite a number of stale branches. We should aim at removing the number of open branches and delete or merge them wherever possible.

@georgii-tishenin
Copy link
Collaborator

Hi, @stv0g, thanks for creating this issue.
To move this forward and eventually close the issue we can:
1. Identify Stale Branches

  • We can use this list of stale branches. These are the branches with >3 months without a commit. Or we could may be use our own more relaxed definition of stale, e.g., 1 year without a commit.

2. Assign Ownership

  • Assign each stale branch to its creator.

3. Set a Response Deadline

  • Give creators 1 month to confirm if their branch is needed or can be deleted.

4. Delete Unclaimed Branches

  • Delete branches with no response after the deadline.

what do you think?

@stv0g
Copy link
Contributor Author

stv0g commented Sep 17, 2024

There are the following stale branches created by you. Can we delete them, or are they still beeing worked on / going to be merged at some point in time?

@dinkelbachjan:

@LennartSchu

@m-mirz

@martinmoraga

@georgii-tishenin

@philipp-fensch

@fwege

This is just a first bunch of the branches. I would say, if we dont receive any feedback within the next 4 weeks, we should delete the branches..

@georgii-tishenin
Copy link
Collaborator

Hi, @stv0g, thanks for driving this further. I removed my stale branch👍

@m-mirz
Copy link
Contributor

m-mirz commented Sep 20, 2024

@stv0g I have moved my branches to my fork as commented in the other PR. Before you delete branches, please let me know which ones. I would like to store them in my fork as well if the original contributors do not follow up on them. I know that considerable effort went into some of them and do not want to lose the work.

@LennartSchu
Copy link

@stv0g I'm not working on any of those branches. I'm not sure either whether either can be deleted. At least one of them is associated with a PR, but I don't know if it will ever be merged. The branches seem to be too divergent from the current master-branch to be useful, I guess.

@stv0g
Copy link
Contributor Author

stv0g commented Sep 20, 2024

@m-mirz @LennartSchu I would delete the branches mentioned in my previous comment. There are still more, but I would like to delete them in smaller batches rather than all at once.

@m-mirz
Copy link
Contributor

m-mirz commented Sep 22, 2024

@stv0g I have stored all of the branches above in my fork as well. So, you can go ahead deleting them if you do not receive feedback.

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