2
One of the main products of my company already has about 4 years of life. In the meantime many branches and tags have been created, and the repository has been migrated from SVN to GIT.
Because of this, the repository has a lot of old code and several branches that were created and never finished or deleted after merging with master.
We are currently looking to develop a number of new features, but not before clearing the repository and the code itself. Hence your experience: how to maintain a well-organized Git repository?
My point of view would be better to delete the old branches ... imagine something ... it happened cmg.... I created a branch but I had not seen that the name of this branch had already been created, I only realized when I went to merge .... imagine the headache that gave ... gets the tip .... wise same is the one who learns from the mistake of others.
– user14100