For teammates that don't have the pleasure of using graphite's PR versioning comparisons, these force pushes can get confusing. In this case, I rebased then added a commit. The first force push is on the base branch, I guess there's no way to silence this in github. The second one shows combined changes from the rebase as well as new changes to my branch, so the compare view is not very useful. Is there any way to crudely replicate Graphite's versioning here? Perhaps separating this into two separate force push operations, one that just rebases the previously submitted branch, then another one that shows actual updates to the PR? I imagine this would involve patching the changes from the last submitted version to the base branch, temporarily moving the local branch head, force pushing that, then moving the branch head back and doing the normal force push. Not sure if this would mess with Graphite's versioning, but if it can be accommodated it'd be a lovely feature for those of us working on teams not fully converted to Graphite yet.