How do I get a personal access token?

On https://www.drupal.org/user/3611150/git, there should be a section to generate a personal access token. On my account page, I can just find a section to generate a password for HTTPS authentication. I cannot say that is the same, as I generated the password, but on git.drupalcode.org I keep seeing this message.

You won't be able to pull or push project code via HTTPS until you create a personal access token on your account

Reading on Git Authentication for Drupal.org Projects, I get this is still to be implemented, but I am not sure the documentation is up-to-date.

smcbain@git.drupal.org/project/coder.get

Git remotes with usernames have been deprecated, and removed now that we’ve launched our GitLab integration. The username before the @ should be replaced with git@. And I assume .get is a typo. Use the instructions on the “Version control” tab of your project page like https://www.drupal.org/project/coder/git-instructions.

You won't be able to pull or push project code via HTTPS until you create a personal access token on your account

This message is a bit misleading, we’re working on removing it. You likely do not need to do anything relating to this warning.

You can push via the SSH Git remote listed on “Version control” tab of projects you maintain. If you are not a maintainer, and HTTPS remote will show on that page. Authentication is not needed to pull from HTTPS Git remotes.

As a maintainer, you can push over HTTPS, which is only recommended if you are unable to use SSH. Generating the password, also known as personal access token, can be done as described in #2. This is different from your Drupal.org login. Do not use your Drupal.org login in a Git client, or anywhere else that is not https://www.drupal.org/user.

Feel free to re-open this issue if https://www.drupal.org/project/coder/git-instructions does not help.

This is still fairly confusing to someone new. For instance, only here is it mentioned that a "Personal Access Token" is actually the password.

And it turns out I didn't need it, as Neil points out. With the SSH keys in, just needed to change the remote repo with:
git remote set-url origin git@git.drupal.org:project/campaign_kit.git

Hah! Just spent 15 minutes hitting my head against the wall trying to figure out where I was supposed to create a "personal access token".

This isn't fixed - the error message still appears at the time of writing.

This support request was about being able to access Git from the command line, and that part has been answered. (That is why this support request has been marked as Fixed.)

Visiting https://git.drupalcode.org/, I don't get anymore the You won't be able to pull or push project code via HTTPS until you create a personal access token on your account. warning I saw before.

Confirming #8. When signed in and visiting the project page of a project I maintain, the error message still appears.

I opened #3056977: Remove “You won't be able to pull or push project code via HTTPS until you create a personal access token on your account” message to track actually suppressing this message from GitLab.

Ditto:

Hah! Just spent 15 minutes hitting my head against the wall trying to figure out where I was supposed to create a "personal access token".

12 months after #12 the issue and the message about personal access token still exists and is still confusing users who are trying to use git. I've gone through setting up SSH keys, and gone through setting up a password. Seems like password is synonymous with personal access token.

If Drupal wants participation they need to make access comprehensible. Aside from doing a patch through the issue queue there doesn't seem to be a path to get access to git on a project. I know that's not true but you have to stop hiding it. In my case it was easier to set up a whole independent project on Github, clone all the files from Drupal's Git area, write a whole new release and invite the maintainer here on Drupal to come clone my whole set of files (which happened), than it was to get push access to Drupal's git for a project.

+1 fkelly - agree 100% :)

Thanks @Alexharries. I have learned to just ignore the warning messages. But, if Drupal wants new people to participate they need to clean up annoyances like this. Not good enough to point the finger at Gitlab.

It appears that the newer Merge feature and the way it works with Git on Drupal is superseding the patch (and have the patch not apply for obscure reasons) approach. Learning to use the merge feature takes time too.

+1 fkelly I am contributing for the first time and have also found this message to be confusing.

https://git.drupalcode.org/ is running an instance of Gitlab; there isn't any other way to fix this, if not fixing the Gitlab code. I am sure Drupal.org would not want to fork Gitlab code (supposing it would be allowed) to fix this.

Just to chime in, five more months and still no change.