Clik here to view.
Answer by storenth for How should you create a patch for an older tag in...
Yeah, your updated workflow is a working solution for the Gitlab! There is proof of my fix-old-tag work in case of cherry-pick (or new commits/fixes):git fetch origin --tags --forcegit checkout -b...
View ArticleAnswer by stan for How should you create a patch for an older tag in source...
There are two ways of handling releases in Git : tags and branches.One argument for tags is that they are immutable (you can only delete/recreate them, whereas branches can keep growing), however, I...
View ArticleAnswer by AnoE for How should you create a patch for an older tag in source...
Checking out version 2.3, applying the patch, tagging it 2.3.1 is exactly what you are going to do.Creating a new head (rather, a new branch) is not a problem whatsoever, it's what git was made for....
View ArticleHow should you create a patch for an older tag in source control?
Let's say I released a version of my software about a year ago and tagged it at 2.3 in Git. So I keep adding features and fixing bugs and before you know it, the software is now at version 3.0. But now...
View Article
