3 ms·
I'm not a fan of merging master -> production for deployments. This means that what you tested in master may not be the same artifact that is deployed to prod.
by ramenmeal 6y ago
I'm not a fan of merging master -> production for deployments. This means that what you tested in master may not be the same artifact that is deployed to prod. You're relying on people to correctly handle merge issues in git. This can become an issue if you have some complex hotfixes that have to happen.
edit: I'd rather trunk based w/ tagging commits for releases.
- donmcronald 6y agoYeah. I wonder if that merge to production rebuilds artifacts. That seems nasty.