61 | | - You cannot correct commits that you have already pushed. Comment on the commit's GitHub page instead. (Modifying your local history causes it to diverge from the public history. Publishing this alternate history would require force-pushing, which we [https://help.github.com/articles/about-protected-branches disallow] because it's [https://git-scm.com/book/en/v2/Git-Branching-Rebasing#The-Perils-of-Rebasing bad practice].) |
| 61 | - You cannot correct commits that you have already pushed to the master branch. Comment on the commit's GitHub page instead. (Modifying your local history causes it to diverge from the public history. Publishing this alternate history would require force-pushing, which we [https://help.github.com/articles/about-protected-branches disallow] because it's [https://git-scm.com/book/en/v2/Git-Branching-Rebasing#The-Perils-of-Rebasing bad practice].) |
| 62 | - On the other hand, its acceptable to modify commits made to a feature branch, for instance as part of the review of the GitHub PR where changes are requested and thus the commits need to be squashed to maintain a single clean commit for the PR changes. In this case you will need to force push the changes back to the feature branch on GitHub, at which point the PR will automatically pick up those changes. |