René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Clarify force-push usage for CPython PRs","articleBody":"As someone who regularly reviews PRs from contributors with varying levels of experience with CPython's workflow, often times I find that they repeatedly squash old commits and force-push to the PR branch each time a new commit or round of commits are added (after it has been opened). In most cases, this makes the history of the PR much more difficult to follow for review purposes.\r\n\r\nI assume that their intention is to \"clean up\" the history and leave a single commit at the end for easier merging, but in reality this doesn't do much to help since core devs typically make use of GitHub's \"Squash and Merge\" feature or automerge via miss-islington to squash the commits.\r\n\r\nGuido mentioned this last year in https://discuss.python.org/t/pep-601-forbid-return-break-continue-breaking-out-of-finally/2239/42, but I just thought about it again after seeing it happen \"out in the wild\" recently across CPython PRs from different contributors.\r\n\r\nIt is mentioned at the end of [section 3.8](https://devguide.python.org/pullrequest/#submitting), but I think it could be made a bit more obvious since this seems to occur rather frequently, and can be disruptive to the PR review process. It's a fairly small, but  repeated cost to core development resources that could be avoided.\r\n\r\nOne idea I had in mind was adding a note to the \"Quick Guide\", in [section 3.2](https://devguide.python.org/pullrequest/#quick-guide), which is likely what many contributors primarily consult and regularly refer back to:\r\n\r\nCurrent:\r\n```\r\nHere is a quick overview of how you can contribute to CPython:\r\n\r\n    Create an issue that describes your change [*]\r\n    Create a new branch in Git\r\n    Work on changes (e.g. fix a bug or add a new feature)\r\n    Run tests and make patchcheck\r\n    Commit and push changes to your GitHub fork\r\n    Create Pull Request on GitHub to merge a branch from your fork\r\n    Review and address comments on your Pull Request\r\n    When your changes are merged, you can delete the PR branch\r\n    Celebrate contributing to CPython! :)\r\n``` \r\n\r\nRecommended:\r\n```\r\nHere is a quick overview of how you can contribute to CPython:\r\n\r\n    Create an issue that describes your change [*]\r\n    Create a new branch in Git\r\n    Work on changes (e.g. fix a bug or add a new feature)\r\n    Run tests and make patchcheck\r\n    Commit and push changes to your GitHub fork\r\n    Create Pull Request on GitHub to merge a branch from your fork\r\n    Review and address comments on your Pull Request (without force-pushing)\r\n    When your changes are merged, you can delete the PR branch\r\n    Celebrate contributing to CPython! :)\r\n```\r\nAny other recommendations for locations that it could be mentioned would also be welcome, but that was the most impactful that I had in mind.","author":{"url":"https://github.com/aeros","@type":"Person","name":"aeros"},"datePublished":"2020-03-21T00:44:12.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/579/devguide/issues/579"}