Unclear how to make Personal Access Token for Git HTTP 2FA
Related issues: https://gitlab.com/gitlab-org/gitlab-ce/issues/26281 https://gitlab.com/gitlab-org/gitlab-ce/issues/26412
When a user account has two-factor authentication (2FA) enabled the user must use personal access tokens when access their Git repositories over HTTP (git push etc.).
We introduced 'scopes' for personal access tokens not so long ago. This has led to a usability problem: it is unclear how to create personal access tokens that work for Git HTTP.
It took me trial and error of four different check box combinations to find out what was needed for Git HTTP. This is not something we should be putting users through.
Possible solutions would be having a separate scope for git access, or a clear indication on the page which scope combo grants git access to a personal access token.