Clone over HTTPS
Authenticate git clone, fetch, and push operations over HTTPS using a personal access token.
Clone and Push over HTTPS
git.eu repositories support standard git clone, fetch, and push over HTTPS. Every HTTPS git operation is authenticated - there is no anonymous write access, and private repositories also require authentication to read.
Authentication Model
HTTPS git operations use HTTP Basic authentication: a username plus a credential in the password field. git.eu accepts two kinds of credential:
| Credential | Best for |
|---|---|
| Personal access token (PAT) | Manual git usage, CI/CD jobs, scripts |
| OAuth token, via a credential helper | Interactive daily use, no token to copy or paste |
This guide covers the PAT method. For the OAuth credential-helper method (automatic, no manual token handling), see Git Access.
Clone or Push with a Token
Step 1 - Create a Token
Create a personal access token from Settings → Tokens - see Method B - PAT in the Git Access guide.
Step 2 - Use It as the Password
Run a normal git command against your instance. When prompted for credentials, enter your username and paste the token as the password:
git clone https://<HOST>/<owner>/<repo>.git
Username: <your-username>
Password: <paste-your-token>
<HOST> with your git.eu instance's hostname, and <owner>/<repo> with the repository path. Never hardcode a real token in a script or commit it to a repository - read it from an environment variable or a CI secret instead.
Using a GUI client such as TortoiseGit, or seeing the Windows credential prompt instead of a terminal prompt? See Git Client Setup for the exact click-by-click steps.
Step 3 - Cache It (Optional)
To avoid the prompt on every operation, configure a system credential helper (git config --global credential.helper store, or your OS keychain helper) - it caches the token after the first successful use.
Next Steps
Ready to get started?
Create a personal access token