4 ms·
I also have found myself in a shop that uses this flow, and don't get me wrong, it works pretty darn well, but it's also just turns PRs/branches into commits an
by Spivak 5y ago
I also have found myself in a shop that uses this flow, and don't get me wrong, it works pretty darn well, but it's also just turns PRs/branches into commits and is effectively a single-branch linear workflow with extra steps. It's the closest thing to not using git that exists.
- preseinger 5y ago> it's also just turns PRs/branches into commits and is effectively a single-branch linear workflow Yes! This is ideal.
- w-j-w 5y agoThis is Continuous Integration or Trunk Based development, and it often shows up in surveys as being a very effective tactic.
- hn_throwaway_99 5y ago> It's the closest thing to not using git that exists. Totally disagree, because the whole reason for this is to support multiple developers working simultaneously of the same master branch. That is, sure, master may just be a linear history of commits, but at any specific point in time there may be 10 feature branches off master, each from a different branch point.