Improvements to Lifecycle of a pull request

I write this issue as a feedback from Euro Python 2024 sprint to denote troubles I encountered as I contributed to cpython.

Describe the enhancement or feature you'd like
Missing content in "Lifecycle of a pull request" https://devguide.python.org/getting-started/pull-request-lifecycle/

• "Quick guide" is missing a step to create NEWS.d record. It's just very briefly mentioned in patchcheck.
• "Step-by-step guide" doesn't denote a branch naming convention. I was told to use gh-<number>-<name>.
• "Making good commits" doesn't mention gh-<number> should be included in the commit message.
• "Step-by-step guide" doesn't mention gh-<number> should be included in the PR title.

Describe alternatives you've considered
None.

Comece pela página vinculada “Lifecycle of a pull request” no Python developer’s guide e revise as seções Quick guide, Step-by-step guide e Making good commits. Atualize a documentação para abordar o NEWS.d record e as convenções de nomenclatura e de mensagens de gh-; considera-se concluído quando os quatro detalhes solicitados do fluxo de trabalho estiverem claramente especificados.