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.

Commencez par la page liée « Lifecycle of a pull request » dans le Python developer’s guide et examinez ses sections Quick guide, Step-by-step guide et Making good commits. Mettez à jour la documentation pour couvrir le NEWS.d record ainsi que les conventions de nommage et de message de gh- ; le travail est terminé lorsque les quatre détails demandés du workflow sont clairement indiqués.