j****r
发帖数: 10 | 1 在每次code release之间的hot fix, 是单独一个branch/tag吗？如果是用git, 是如何
规划不同repo的，特别是如果有多个env，怎么manage 那些site specific的code/
config？ | g*****g
发帖数: 34805 | 2 Ideally you only need one branch if you have continuous delivery capability.
The reason is that as long as all tests are passed, you can push any time
you want. And you can have as many feature branches as you need. Release is
tagged, and a hot fix branch is no different from a feature branch.
If you have multiple env, I am assuming for prod/dev/test/canary purpose,
you can have different configs for different environments, and pass in a
runtime variable to determine which environment it is in.
【在 j****r 的大作中提到】
: 在每次code release之间的hot fix, 是单独一个branch/tag吗？如果是用git, 是如何
: 规划不同repo的，特别是如果有多个env，怎么manage 那些site specific的code/
: config？
|
|
