Skip to content
Snippets Groups Projects
Select Git revision
  • main
1 result

gitlab-token-doc

  • Clone with SSH
  • Clone with HTTPS
  • Christian Krause's avatar
    ck85nori authored
    878a632f
    History
    Name Last commit Last update
    LICENSE
    README.md

    GitLab Tokens

    general recommendations

    1. Use a separate token for each device and do not share tokens across devices.

    2. Split token permissions (aka scopes), e.g. use a separate token for push/pull access and for API access.

    git clone / push / pull

    1. go here to generate tokens

    2. hit the Add new token button

      • Name: git over http DEVICE_NAME
      • Expiration date: a month or a year, depending on security implications of what you're doing
      • Scopes: select read_repository and write_repository

      then, hit the Create personal access token button

    3. GitLab shows Your new personal access token along with a copy/clipboard button.

      Note: This is the only time GitLab will allow you to see/copy the token content!

      Copy the token in your password manager of choice / wherever you're asked to authenticate. When correctly set up, git will save the token in your password manager of choice.