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.

Localize a passagem do developer guide que aborda git push origin <branch name> e leia as instruções de autenticação ao redor dela. Atualize-a para explicar GitHub personal access tokens no prompt de senha, usando a documentação do GitHub vinculada; considera-se concluído quando os iniciantes forem informados de que não devem inserir sua senha normal do GitHub.