I'm struggling to understand why they aren't just using a typical git flow model and merging to a separate develop branch. They could even setup a git hook to automatically cut releases to master...
I'm struggling to understand why they aren't just using a typical git flow model and merging to a separate develop branch. They could even setup a git hook to automatically cut releases to master after x number of merges. It seems like this would solve most, if not all, of their requirements.
What unique problem does shopify have that requires using this tool for? The only thing that I can think of is that it lets developers "merge" their PR without having their test pass first, which is important because they suffer from a lot of flaky tests. I can at least empathize with that. Having to rebuild your PR branch 2+ times because of random, unrelated test failures sucks.
I'm struggling to understand why they aren't just using a typical git flow model and merging to a separate develop branch. They could even setup a git hook to automatically cut releases to master after x number of merges. It seems like this would solve most, if not all, of their requirements.
What unique problem does shopify have that requires using this tool for? The only thing that I can think of is that it lets developers "merge" their PR without having their test pass first, which is important because they suffer from a lot of flaky tests. I can at least empathize with that. Having to rebuild your PR branch 2+ times because of random, unrelated test failures sucks.