If I create a Pull Request from a branch
git checkout -b branch-for-first-PR
# edits and commits
git push origin branch-for-first-PR
do some work in it, and then want to experiment with building on that while the first PR is getting reviewed I might do
git checkout branch-for-first-PR
git checkout -b branch-for-second-PR
# edits and commits
git push origin branch-for-second-PR
The problem that I'm having is that the diffs for the second PR show all the changes in the first which is confusing for reviewers.
Is there a structured way to indicate to code review tools (I'm just using Github at this point) that one patch depends on another patch under review? Ideally something like Google's internal DIFFBASE=
that gives the reviewer the option of ignoring hunks that are unchanged from the first PR.