This is particularly useful when doing async peer reviews, where the `at a glance` diff view provides enough insight to provide that inline feedback, prior to any further due-diligence via checking out that branch.
There are regularly scenarios where feature branches may fast-track merges from other feature branches, in turn, making the PR harder to read as its not clear what changes are relevant to the branch and what were merged. This could obviously be worked around by creating PRs into other feature branches, but ideally, we want them all to develop.
Being able to narrow down the diff viewer would be super valuable. `packages/inspace-mapping` for example, could restrict to only the diffs within that scope. or just `packages/`, `apps/` etc.
Suggestion
This is particularly useful when doing async peer reviews, where the `at a glance` diff view provides enough insight to provide that inline feedback, prior to any further due-diligence via checking out that branch.
There are regularly scenarios where feature branches may fast-track merges from other feature branches, in turn, making the PR harder to read as its not clear what changes are relevant to the branch and what were merged. This could obviously be worked around by creating PRs into other feature branches, but ideally, we want them all to develop.
Being able to narrow down the diff viewer would be super valuable. `packages/inspace-mapping` for example, could restrict to only the diffs within that scope. or just `packages/`, `apps/` etc.