Set up keys

To commit from your local IDE or CLI, developers must set up the following keys:

• Sign commits with a GPG Key
• Use SSH keys to communicate with GitLab

From 15 January 2026, if you are committing using Web IDE, your commits are signed by GitLab automatically. For details, see Signed commits in the GitLab web interface (IDE).

Git authentication

To perform Git operations, authenticate using one of the following methods:

• Personal Access Token (PAT) — for Git over HTTP(S)
• SSH key — for Git over SSH

Note: Using your GitLab account password is not supported.

Check your current authentication method

Check your system’s credential store for your locally stored Git credentials.

• macOS: Open Keychain Access and search for sgts.gitlab-dedicated.com.
• Windows: Open Credential Manager > Windows Credentials and look for a git:https://sgts.gitlab-dedicated.com entry.
• Linux: Run git credential-store or check ~/.git-credentials if you are using the store helper. Look for entries where the password field is your account password rather than a Personal Access Token.

If the stored password is your account password rather than a glpat- prefixed token, switch to a PAT or SSH key using the steps below.

Switch to Personal Access Token (Git over HTTP(S))

If you don’t have a Personal Access Token yet, create one in GitLab first. Then, in your credential store (see Check your current authentication method), replace the saved password with your PAT.

Switch to SSH key authentication (Git over SSH)

1. Generate an SSH key and add it to your GitLab account.

2. Update your local repository remote URL to use SSH:

   git remote set-url origin git@sgts.gitlab-dedicated.com:<namespace>/<project>.gitCopy to clipboardErrorCopied

Automations and pipelines using project, group, or service account access tokens for Git authentication over HTTP(S) are not affected.

Next steps

• Configure CI/CD pipelines