|
|
|
|
|
by btreecat
4017 days ago
|
|
To me (a mercurial user mostly) this is kind of like a "no duh" article having never read the original "gitflow." I think that is because I am used to using hg's branches, bookmarks, and tags for different use cases. If I want to mark a revision as a particular release number (which is something we don't really do here but I can see the value) then I would use hg tag. Tag's are permanent. If I want to mark a revision as "production" and then have some automated process take over based on the the updated info, I would use hg bookmark. Bookmarks are the closest equivalent to git's branches. Bookmarks can be updated to a new revision or removed. If I wanted to work on a parallel branch of development for an experimental feature or if I am attempting to upgrade some dependencies, I can use hg branch. This creates a named branch in the code base which is permanent. This branch can eventually be either closed or merged back into the main. |
|