tl;dr you can put commit hashes in the place where the parent comment put tags, and your exact use case actually has a dedicated link on the PR page. The PR in

tl;dr you can put commit hashes in the place where the parent comment put tags, and your exact use case actually has a dedicated link on the PR page. The PR interface actually exposes this for force-pushes, but the UI discovery for this is horrible. It turns out that the "force-pushed" part in the little message in the github UI is actually a link. This link points to the diff between the old and the new HEAD of the branch. As an example you can look at this PR: https://github.com/JelteF/derive_more/pull/161 https://github.com/JelteF/derive_more/pull/161 It has this little message somewhere down the page: Monadic-Cat force-pushed the add-unwrap branch from e130dbe to 25235aa 4 months ago If you then click "force-pushed" in that message you go to the "compare" page, which shows the diff between the two commits: https://github.com/JelteF/derive_more/compare/e130dbe6b2a42939245106e9f6934bd903d882ca..25235aaf7714897111969a79f8b63f2c3f8f574e https://github.com/JelteF/derive_more/compare/e130dbe6b2a429... Disclaimer: I'm a Micrsoft employee, but don't work on Github. I'm a daily user of Github though.