Improvement to Lifecycle of a Pull Request at git push origin

Where:

When all of your changes are committed (i.e. git status doesn’t list anything), you will want to push your branch to your fork:

git push origin <branch name>

This will get your changes up to GitHub.

There is a step missing which gave me some issue. That is the bit about the git command responds with username and password. If you enter your GitHub password the response is:

Username for 'https://github.com':
Password for 'https://@github.com':
remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead.
remote: Please see https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/ for more information.
fatal: Authentication failed for 'https://github.com//cpython.git/'

So I suggest adding enough info to get the beginners around this such that the page now reads:

Ensure that you have created a personal access token link.
Note that you will likely need the token until your changes have been accepted.
When all of your changes are committed (i.e. git status doesn’t list anything), you will want to push your branch to your fork:

git push origin <branch name>

At the password prompt:
Password for 'https://@github.com':

Enter you personal access token (ghp_1e3f...) instead of your usual GitHub password.
This will get your changes up to GitHub.

找到介绍 git push origin <branch name> 的 developer guide 段落，并阅读其周围的身份验证说明。使用链接的 GitHub 文档更新该段落，说明在密码提示处使用 GitHub personal access tokens；当新手被告知不要输入其普通 GitHub 密码时，即视为完成。