Skip to content

Update pull-request-lifecycle.rst with creating PR title and descriptions (#931) - #1626

Open
gioviebell wants to merge 4 commits into
python:mainfrom
gioviebell:main
Open

Update pull-request-lifecycle.rst with creating PR title and descriptions (#931)#1626
gioviebell wants to merge 4 commits into
python:mainfrom
gioviebell:main

Conversation

@gioviebell

@gioviebell gioviebell commented Aug 9, 2025

Copy link
Copy Markdown

Updated the "making a good PR" section of the page with tips on creating the title and description

#931

📚 Documentation preview 📚: https://cpython-devguide--1626.org.readthedocs.build/

Updated the "making a good PR" section of the page with tips on creating the title and description
@python-cla-bot

python-cla-bot Bot commented Aug 9, 2025

Copy link
Copy Markdown

All commit authors signed the Contributor License Agreement.

CLA signed

issue resolution. It is the initial point of contact in a code review, and
allows the code reviewer to quickly assess the issue. The suggested formatting
of the title and description is
**[type(optional) title: description (issue number)]** where type is the label

@StanFromIreland StanFromIreland Aug 9, 2025

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't understand this, where is the gh-XXXXX, and what is type?

An example title:

GH-132732: Use pure op machinery to optimize various instructions with _POP_TOP and _POP_TWO

Updated the title formatting, and provided an example. Also removed trailing whitespaces.
pythonGH-931: Update pull-request-lifecycle.rst PR title and description section
Comment on lines +232 to +234
Here is an example of a poor and revised pull request description:
**Poor Pull Request:** "update code" **Revised Pull Request:**
"feat: add search functionality to user dashboard(closes #111)"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This has the same issue I mentioned above (which was correct).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants