Some high-level description is what this actually does would be useful.
The main problem with "stacked diffs" or "dependent pull reviews" on GitHub is that they don't work with forks/clones.
That is: you can push a branch to your personal clone and then submit a PR against the main repository's development branch. That works fine.
You can push two stacked branches into the main repository and set up dependent pull requests (where pr1 targets the main development branch and pr2 targets pr1). That sort of works -- lots of things could be improved about the UI of that workflow, but it's at least possible to do.
You can't reasonably push two stacked branches to your personal clone and then set up dependent pull requests against the main development branch: pr2 that targets pr1 will simply not show up in the main repository.
Given the fact that the original use case of Git is to work with "stacked diffs", it's absolutely mind-blowing that GitHub still has no property sort for it.
Comments
Some high-level description is what this actually does would be useful.
The main problem with "stacked diffs" or "dependent pull reviews" on GitHub is that they don't work with forks/clones.
That is: you can push a branch to your personal clone and then submit a PR against the main repository's development branch. That works fine.
You can push two stacked branches into the main repository and set up dependent pull requests (where pr1 targets the main development branch and pr2 targets pr1). That sort of works -- lots of things could be improved about the UI of that workflow, but it's at least possible to do.
You can't reasonably push two stacked branches to your personal clone and then set up dependent pull requests against the main development branch: pr2 that targets pr1 will simply not show up in the main repository.
Given the fact that the original use case of Git is to work with "stacked diffs", it's absolutely mind-blowing that GitHub still has no property sort for it.