Skip to main content

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.

3
  • Thanks for the response! Before I go ahead and implement it this way, I just want to run the actual issue by you to see if you have any ideas. The specific problem is with release branches containing changes not being brought back into our development branch. The initial thought was that we could create a hook that would trigger when creating a branch whose name is similar to another remote branch. This way, we just need to require that release branches use the same naming style, and then the dev will be forced to delete the branch, prompting him to merge in any changes. Commented Nov 11, 2014 at 22:31
  • Another thought was to have a perpetual release branch. The downside being that our release branch could contain code not present in our dev branch. Thoughts? Commented Nov 11, 2014 at 22:36
  • You may have already seen it but it's so good you never overlook it: nvie.com/posts/a-successful-git-branching-model Commented Nov 12, 2014 at 4:12