Replace the PR quickguide with a link

Instead of a duplicate guide, we can now link to the canonical quick
reference doc.

Author: sirosen

getting-started/pull-request-lifecycle.rst

@@ -16,58 +16,8 @@ that you create a branch in Git, make your changes, push those changes
 to your fork on GitHub (``origin``), and then create a pull request against
 the official CPython repository (``upstream``).
 
-
-.. _pullrequest-quickguide:
-
-Quick guide
-===========
-
-`Clear communication`_ is key to contributing to any project, especially an
-`Open Source`_ project like CPython.
-
-Here is a quick overview of how you can contribute to CPython:
-
-#. `Create an issue`_ that describes your change. If it is trivial
-   (like :ref:`typo fixes <typo-fixes>`), or an issue already exists,
-   you can skip this step.
-
-#. :ref:`Create a new branch in Git <pullrequest-steps>` from the
-   ``main`` branch
-
-#. Work on changes: fix a bug or add a new feature
-
-#. :ref:`Run tests <runtests>` and ``make patchcheck``
-
-#. :ref:`Commit <commit-changes>` and :ref:`push <push-changes>`
-   changes to your GitHub fork
-
-#. `Create Pull Request`_ on GitHub to merge a branch from your fork
-
-#. Make sure the :ref:`continuous integration checks on your Pull Request
-   are green <keeping-ci-green>` (successful)
-
-#. Review and address `comments on your Pull Request`_
-
-#. When your changes are merged, you can :ref:`delete the PR branch
-   <deleting_branches>`
-
-#. Celebrate contributing to CPython! :)
-
-Don't force-push
-----------------
-
-In order to keep the commit history intact, please avoid squashing or amending
-history and then force-pushing to the PR. Reviewers often want to look at
-individual commits.
-When the PR is merged, everything will be squashed into a single commit.
-
-.. _Clear communication: https://opensource.guide/how-to-contribute/#how-to-submit-a-contribution
-.. _Open Source: https://opensource.guide/
-.. _create an issue: https://github.com/python/cpython/issues
-.. _CPython: https://github.com/python/cpython
-.. _use HTTPS: https://help.github.com/articles/which-remote-url-should-i-use/
-.. _Create Pull Request: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request
-.. _comments on your Pull Request: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request
+For a cheat-sheet reference, see the
+:ref:`quick reference on creating pull requests <pullrequest-quickguide>`.
 
 
 .. _pullrequest-steps:

getting-started/quick-reference.rst

@@ -93,6 +93,8 @@ Run the tests
 See also :ref:`how to write and run tests <run-write-tests>`.
 
 
+.. _pullrequest-quickguide:
+
 Create issues and pull requests
 ===============================
 
@@ -166,7 +168,9 @@ See also, GitHub's documentation on `commenting on Pull Requests`_.
 
 .. note::
 
-   Don't force-push. Reviewers often want to look at individual commits.
+   In order to keep the commit history intact, please avoid squashing or amending
+   history and then force-pushing to the PR.
+   Reviewers often want to look at individual commits.
 
    CPython uses squash merges, so PRs will end up as single commits when merged.