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
  • I can see where you're coming from RE the example about production crashing but if you're going to redeploy without making changes then you'll have the original artifacts to deploy from, the branch won't be required. If you need to hotfix a production issue then you can pull using the release tag of the version that is on production. I guess there are solutions for every scenario someone comes up with and if your answer is the best practice then I would be happy with that. Commented Apr 1, 2020 at 7:39
  • I think the quote you have referenced answers my question and this can be considered the best practice when using gitflow. "We consider origin/master to be the main branch where the source code of HEAD always reflects a production-ready state". In other words, don't merge the release into master until it has been signed off my the client. Thanks Commented Apr 1, 2020 at 7:55
  • That's a good point about using tags. We don't use them where I currently work, but I can see the value. RE keeping the build artifact, another good point, but I can still imagine a scenario where the required artifact is no longer around and must be rebuilt from the master branch. Commented Apr 1, 2020 at 14:32