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.
- 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.Percy– Percy2020-04-01 07:39:41 +00:00Commented 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. ThanksPercy– Percy2020-04-01 07:55:51 +00:00Commented 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.Kyle McVay– Kyle McVay2020-04-01 14:32:58 +00:00Commented Apr 1, 2020 at 14:32
Add a comment |
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you