-
Notifications
You must be signed in to change notification settings - Fork 879
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
Branch clean up #1653
Comments
I have always created branches under my own fork (which is very messy anyway). Based on the names, I think these can be removed:
Though I think I created this one: origin/base_ci_cache_experiment. |
Thank you @rht Did some digging... here is a list of branches with the last commit date, the author of the commit and the branch name.
Output:
I was trying to figure out a way to check if a branch has a open PR using jk/testbranch as the one that I know does, but I can't find a good command to do that. I guess it is small enough to do manually. I will probably divide by year. This week - 2017. ... Also @Corvince, please let us know if you are aware of a particularly interesting or valuable branch for whatever reason. |
Test for search: https://github.com/projectmesa/mesa/pulls?q=is%3Apr+is%3Aopen+head%3Ajk%2Ftestbranch+ I am not worried about this branch, so I am going to use this as demo to show how I might approach the others.
deleted. |
Branches that were cleaned out today: release_fix All branches were searched for in repo in the following matter: test for search: https://github.com/projectmesa/mesa/pulls?q=is%3Apr+is%3Aopen+head%3Aghost_flockers |
I did a run of latest commits to branches. I know there are a few associated with you making the last commit. 02/19/2019 09:27 AM Corvince Fix-#644 |
update-pipfile (confirmed) |
Updated list on what is left -
|
I made a pass over all branches and removed very stale or already merged branches. |
We have a lot of branches. We should do a clean up. When something is cleaned OR decided to not be (eg main) please mark off the list below.
The text was updated successfully, but these errors were encountered: