4 ms·
> When you're ready to deploy your new code, you should always deploy your branch before merging. Always. Does anyone actually do this? This seems counterprod
by softawre 11y ago
> When you're ready to deploy your new code, you should always deploy your branch before merging. Always.
Does anyone actually do this? This seems counterproductive - what if there are multiple branches?
- datr 11y agoI've worked places where we will always deploy a feature request to an ephemeral environment. I find quite a lot of bugs are actually caught by this. But I've never deployed a feature branch into production like the blog post suggests. I had my own questions about this lower down in the comments.
- NLips 11y agoAssuming you have a product/release branch and many others, then I'm guessing the author means you should merge product into your own branch and deploy that, before merging your branch back into product (and deploying it). That should work fine with multiple branches in most cases, so long as you have a system to stop anyone else deploying their branch while yours is running.