4 ms·
Do you use any special tools for this? I've heard of people "stacking" diffs in this way, but it seems like it would be clunky to review on GitHub.
by RussianCow 4y ago
Do you use any special tools for this? I've heard of people "stacking" diffs in this way, but it seems like it would be clunky to review on GitHub.
- return_to_monke 4y agoThis is one of the features of (yes), Meta's sapling VCS. https://sapling-scm.com/docs/introduction/getting-started/ https://sapling-scm.com/docs/introduction/getting-started/
- Dunedan 4y agoIf you work directly in the source repository that works actually really well on Github (if everybody works on its own fork instead, you're unfortunately out of luck). When opening a pull request, you just select the branch the pull request should be based on to be the previous branch in your stack. If one of those pull requests gets merged, Github will automatically rebase the stacked on onto the base branch. This way every pull requests contains exactly the changes you want it to contain, while you're still being able to stack changes by opening multiple pull requests, with each one being based on the branch of the previous one.
- kevingoslar 4y agoI use https://www.git-town.com/nested-feature-branches.html https://www.git-town.com/nested-feature-branches.html.