@@ -42,6 +42,25 @@ a discussion venue appropriate to the PEP (such as `Typing Discourse
42
42
typing, or `Packaging Discourse <https://discuss.python.org/c/packaging/ >`__
43
43
for packaging), or `open an issue <https://github.com/python/peps/issues >`__.
44
44
45
+ Opening a pull request
46
+ ----------------------
47
+
48
+ The PEPs repository defines a set of pull request templates, which should be
49
+ used when opening a PR.
50
+
51
+ If you use Git from the command line, you may be accustomed to creating PRs
52
+ by following the URL that is provided after pushing a new branch. **Do not use
53
+ this link **, as it does not provide the option to populate the PR template.
54
+
55
+ However, you *can * use the ``gh `` command line tool. ``gh pr create `` will allow
56
+ you to create a pull request, will prompt you for the template you wish to use,
57
+ and then give you the option of continuing editing in your broswer.
58
+
59
+ Alternatively, after pushing your branch, you can visit
60
+ `https://github.com/python/peps <https://github.com/python/peps >`__, and follow
61
+ the link in the notification about recent changes to your branch to
62
+ create a new PR. The in-browser interface will allow you to select a PR template
63
+ for your new PR.
45
64
46
65
Commit messages and PR titles
47
66
-----------------------------
@@ -56,7 +75,7 @@ the Readme/Contributing Guide, issue/PR template, etc., with ``Meta:``.
56
75
Sign the Contributor License Agreement
57
76
--------------------------------------
58
77
59
- All contributors need to sign the
78
+ All contributors need to sign the
60
79
`PSF Contributor Agreement <https://www.python.org/psf/contrib/contrib-form/ >`_.
61
80
to ensure we legally accept your work.
62
81
0 commit comments