I really like the idea, but I find that there is a big gap in the tooling to do this (and make it easy to review)
It would be nice to open just one PR with several sets of changes where you could provide context for each set of changes.
With GitHub you could do this by having a commit per each set of changes, but you can't add a description for each commit.
You end up having a PR that points to the previous PR, and then you have to decide if you run CI in that PR or just the last PR, and then having some merge issues. With all this hassle people usually just open a big PR with all the changes or decide against doing that small refactor (because it would have to do it in another PR and the hassle is not worth it), overall this ends up decreasing code quality in the codebase.
It would be nice to open just one PR with several sets of changes where you could provide context for each set of changes.
With GitHub you could do this by having a commit per each set of changes, but you can't add a description for each commit.
You end up having a PR that points to the previous PR, and then you have to decide if you run CI in that PR or just the last PR, and then having some merge issues. With all this hassle people usually just open a big PR with all the changes or decide against doing that small refactor (because it would have to do it in another PR and the hassle is not worth it), overall this ends up decreasing code quality in the codebase.