| > Yes you do need to run `git rebase --update-refs` constantly but you want your commits to be meaningful enough to be preserved, you are doing the rebase anyways. If you don't want to type `--update-refs` put it in your .gitconfig. I tried out that config for a while but it was too much of a sledgehammer in practice. It rewrote things that I didn’t want. > And what do you mean vanilla forge PRs don't support it? Hmm. This is what I would call support: - Push one time and you get the option from the remote to generate X dependent PRs since the remote sees that you have some branch tip and X-1 ancestor branches which are not in `main`... etc. I at least haven’t heard of this support in GitHub. What does not rise to that level: having to create X PRs manually and making sure to target each of them individually. But apparently the Git experts (or simply the ones who do not suck at it) do this with vanilla tooling. I could very well be missing something here. > If it's GitHub you simply tell your reviewer to look at the commit diff view not the PR diff view. You mean a five-commit PR could be a one-commit-per-PR by saying to the reviewer “look at the commit diff”? Then I have no trouble with it. |