As explained in using gitlab token to clone without authentication, you can clone a GitLab repo using your Personal Access Token like this:
git clone https://oauth2:ACCESS_TOKEN@gitlab.com/yourself/yourproject.git
As for how to update your existing clones to use the GitLab Personal Access Token, you should edit your .git/config file in each local git directory, which will have an entry something like this:
[remote "origin"]
url = https://yourself@gitlab.com/yourself/yourproject.git
Change the url:
[remote "origin"]
url = https://oauth2:ACCESS_TOKEN@gitlab.com/yourself/yourproject.git
Now you can continue using this existing git clone as you did before you enabled 2FA.
Personal access tokens on GitLab
If you’re unable to use OAuth2, you can use a personal access token to authenticate with the GitLab API. You can also use a personal access token with Git to authenticate over HTTP.
In both cases, you authenticate with a personal access token in place of your password.
Personal access tokens are required when Two-Factor Authentication (2FA) is enabled.
For examples of how you can use a personal access token to authenticate with the API, see the API documentation.
Alternately, GitLab administrators can use the API to create impersonation tokens. Use impersonation tokens to automate authentication as a specific user.
Create a personal access token
You can create as many personal access tokens as you like.
- In the top-right corner, select your avatar.
- Select Edit profile.
- In the left sidebar, select Access Tokens.
- Enter a name and optional expiry date for the token.
- Select the desired scopes.
- Select Create personal access token.
Save the personal access token somewhere safe. After you leave the page, you no longer have access to the token.