Remove redundant repository branches
See original GitHub issueControlsFX repository has the following branches:
master
- previous default branch, used for Java 8 development9.0.0
- Forked out of master, contains changes for JDK 9 and laterjfx-13
- Current default branch. Forked out of 9.0.0 branch and contains changes for JDK 11 and laterrevert-1139-patch-1
- Stale branch
Since all development and bug fix effort is targeted on jfx-13
, my proposal is to:
- Remove all branches except
jfx-13
- Rename
jfx-13
to something generic:master
ormain
- All tags will remains intact
This issue is to gather community feedback and keep track of the progress.
@Maxoudela @eugener your feedback is appreciated.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Git housekeeping: remove "redundant" branches from the ...
Execute the git remote branch delete command for each element in the list. Script to clean up the local repository. If you have...
Read more >Purging redundant branches from git - Stack Overflow
List all local branches that are merged. To get a list of branches that have already been merged with the upstream master: ·...
Read more >Use branch cleanup techniques - Manage Your Code Project ...
Use git prune to remove orphaned/unused branches ... You can use the git prune command to remove orphaned branches. Orphaned branches are branches...
Read more >How To Clean Up Git Branches - devconnected
Force Delete Unmerged Git Branches ... The other way of cleaning up local branches on Git is to use the “git branch” command...
Read more >TIL: Cleaning your Git repository by removing the unused ...
This is pretty useful, and GitHub also deals with it quite nice by deleting the merged branches... but that doesn't happen on your...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
That sounds good.
I have no opinion on the Github flow versus GitFlow. Maybe a bit in favor of having only
master
, especially if we are already following it and our release process is already up to date.Thanks a lot @abhinayagarwal for all the effort and the time you take to maintain this project. Kudos !
Protected branches is definitely a strong advantage and keeps production branches away from unwanted changes. However, I am biased towards the TAG approach as the release automation is already running based on TAGs 😇
I will start working on this issue by removing the branches and renaming
jfx-13
tomaster
. This will most probably break the local repositories for everyone. I apologize in advance for this.