A developer shares a practical CLI-based workflow for reviewing pull requests more effectively when using web-based Git hosting (likely Azure DevOps). The core problem: after a force push that amends commits, reviewers must re-review everything. The solution uses git commands to snapshot the branch before and after the force push, then uses `git range-diff` to compare iterations. For messy commit histories, `git diff origin/master` is used instead. An additional tip pipes `git log -p --reverse` into vim with mail filetype for annotating reviews before copying comments into the web UI.
369 Impressions