Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • 10
    He's using gitflow workflow so manage branches should not be considered an advanced topic - it is part of the core command his developers need to understand. Git in general treat branch management as something basic rather than advanced. Commented Jun 26, 2017 at 14:46
  • 5
    @slebetman: Giving it a name doesn't make it any less complicated or difficult. Commented Jun 26, 2017 at 15:02
  • 3
    You mention "handle local commits" as something more advanced users will need. Theoretically managing versions in your own computer should be a notch lower in the difficulty scale that managing versions in a remote repo, shared with other coders. Commented Jun 26, 2017 at 15:59
  • Maybe if you work somewhere that has a full-time release manager then you don't need to worry about branches, but anywhere else devs should be pushing features to a testing branch each cycle, merging high-priority fixes from the testing branch to the development branch, and doing releases to production off the testing branch. Commented Jun 27, 2017 at 3:35
  • @RobertHarvey: Branching is neither complicated nor difficult. It's basic. The gitflow workflow is complicated in corner cases like bugfix releases but the common use-case is simple. Commented Jun 27, 2017 at 4:02