Clone over HTTPS

Authenticate git clone, fetch, and push operations over HTTPS using a personal access token.

Clone and Push over HTTPS

Clone, fetch, and push over HTTPS with a personal access token (PAT) - the right choice for scripts, CI jobs, and GUI clients. For interactive daily use, the OAuth helper in Git Access needs no token at all.

Step 1 - Create a Token

Open Settings → Git Access → Tokens and create a token. Keep Git access checked (the default, for clone, fetch, and push); API access is not needed for git - it only unlocks The git.eu API. Copy the raw value immediately - it is shown exactly once.

Open Settings → Git Access → Tokens

Step 2 - Use It at the Prompt

Run a normal git command; enter your username and paste the token as the password:

git clone https://<INSTANCE>.git.eu/<USERNAME>/REPO_NAME.git
Username: <USERNAME>
Password: <paste-your-token>

Never hardcode a real token in a script or commit it - read it from an environment variable or a CI secret.

Using a GUI client such as TortoiseGit, or seeing the Windows credential prompt? See Git Client Setup for the click-by-click steps.

Step 3 - Or Put It in the URL

Embed the token in the clone URL - <pat> is the literal token you copied:

git clone https://<USERNAME>:<pat>@<INSTANCE>.git.eu/<USERNAME>/REPO_NAME.git

Migrate an existing repository the same way, after creating the empty one on your instance:

git remote remove origin
git remote add origin https://<USERNAME>:<pat>@<INSTANCE>.git.eu/<USERNAME>/REPO_NAME.git
git push --mirror origin

Warning - the URL form leaks the secret. The URL ends up in your shell history, in the remote configuration (.git/config), and in git error output. Revoke the token from Settings → Git Access → Tokens the moment it appears anywhere it should not.

Step 4 - Cache It (Optional)

Store the token after the first successful use, so git stops asking:

git config --global credential.helper store

Warning - plaintext on disk. The store helper writes the token to ~/.git-credentials unencrypted. Use your OS keychain helper (osxkeychain, wincred, libsecret) instead when available, and revoke the token when the machine is retired or compromised.

Large files? See Git LFS - it uses the same credentials.

Troubleshooting

Use a Personal Access Token as your password. You entered your account password. Paste a token instead. See Use a Personal Access Token.

remote: Access denied (403). The token lacks the Git access scope, was revoked or expired, or you only have read access. See Access Denied (403).

could not read Username. git had no credential and could not prompt (CI, scripts). See Could Not Read Username.

Every other HTTPS sign-in error, with its fix: Knowledge Base - HTTPS Authentication.

About

Every HTTPS git operation is authenticated - no anonymous write, and private repositories also need authentication to read. HTTPS uses HTTP Basic authentication: your username plus a credential in the password field.

Credential	Best for
Personal access token (this guide)	CI/CD jobs, scripts, GUI clients
OAuth token, via a credential helper (Git Access)	Interactive daily use, no token to copy

<INSTANCE> (your instance slug) and <USERNAME> (your account name) resolve automatically in commands and buttons when you are signed in on this site; otherwise swap them for your own values. REPO_NAME is the repository name.

Next Steps

Ready to get started?

Manage your tokens