3 ms·
Also this is a problem with Git not GitFlow. In Mercurial, for example, every commit is attached to a branch so it's very easy to follow where the changes happe
by giulianob 11y ago
Also this is a problem with Git not GitFlow. In Mercurial, for example, every commit is attached to a branch so it's very easy to follow where the changes happened.
- ryanthejuggler 11y agoIronically, for that reason, GitFlow would work better in Mercurial. Go figure.
- davidism 11y agoHgFlow already exists and is actively developed: https://bitbucket.org/yujiewu/hgflow/wiki/Home https://bitbucket.org/yujiewu/hgflow/wiki/Home. It even goes above and beyond GitFlow and adds generalized streams and sub-streams. I've never had to use those extra features, but the core model works well.
- glandium 11y agoMercurial branches are not meant to be used for short-lived feature branches, though. As "hg branch" puts it: "branches are permanent and global, did you want a bookmark?".
- giulianob 11y agoYou can close a branch and it will not show up as being active but you still have the info for every commit which is what makes history readable.