Skip to content

Meta: Further tweak PR template titles to get the right order #3001

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Feb 25, 2023
Merged

Meta: Further tweak PR template titles to get the right order #3001

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ec3a363
Further tweak the PR template titles to get the right order
CAM-Gerlach Feb 1, 2023
b5d008d
Further refine New PEP PR checklist text
CAM-Gerlach Feb 3, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Further refine New PEP PR checklist text
  • Loading branch information
@CAM-Gerlach
CAM-Gerlach committed Feb 3, 2023
commit b5d008d6751bbba7d94aef38320009e1de88b53a
8 changes: 4 additions & 4 deletions .github/PULL_REQUEST_TEMPLATE/Add a new PEP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,9 +13,9 @@ If your PEP is not Standards Track, remove the corresponding section.
* [ ] File created from the [latest PEP template](https://github.com/python/peps/blob/main/pep-0012/pep-NNNN.rst?plain=1)
* [ ] PEP has next available number, & set in filename (``pep-NNNN.rst``), PR title (``PEP 123: <Title of PEP>``) and ``PEP`` header
* [ ] Title clearly, accurately and concisely describes the content in 79 characters or less
* [ ] ``PEP``, ``Title``, ``Author``, ``Status`` (``Draft``), ``Type`` and ``Created`` headers filled out correctly
* [ ] Core dev/PEP editor listed as ``Author`` or ``Sponsor``, and formally confirmed their approval
* [ ] ``Author``, ``Status`` (``Draft``), ``Type`` and ``Created`` headers filled out correctly
* [ ] ``PEP-Delegate``, ``Topic``, ``Requires`` and ``Replaces`` headers completed if appropriate
* [ ] Core dev/PEP editor listed as author or sponsor, and formally confirmed their approval
* [ ] Required sections included
* [ ] Abstract (first section)
* [ ] Copyright (last section; exact wording from template required)
Expand All @@ -37,6 +37,6 @@ If your PEP is not Standards Track, remove the corresponding section.
* [ ] Reference Implementation
* [ ] Rejected Ideas
* [ ] Open Issues
* [ ] ``Python-Version`` set to valid (pre-beta) future Python version
* [ ] Any project stated in the PEP as supporting/endorsing/benefiting from it confirms such
* [ ] ``Python-Version`` set to valid (pre-beta) future Python version, if relevant
* [ ] Any project stated in the PEP as supporting/endorsing/benefiting from the PEP formally confirmed such
* [ ] Right before or after initial merging, [PEP discussion thread](https://peps.python.org/pep-0001/#discussing-a-pep) created and linked to in ``Discussions-To`` and ``Post-History``
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy