A Git repository can be private and secured, which makes it impossible for non-authenticated users to clone it, pull remote commits, and push their local commits. If you need to interact with such a repository, then Hackolade Studio prompts you for your credentials when needed.
Note that Hackolade Studio does not store your Git credentials: your Git client does, in the credential store that it has been configured to use. If you are repeatedly prompted for credentials, then it could be that the option to use the credential manager was disabled during the Git installation process (see pre-requisites). The easiest solution is to re-install the Git client with the credential manager.
HTTPS username and password
If your repository has an HTTPS URL, then you might have to provide the username and password that you use to connect to the Git platform that hosts your private repository (e.g. GitHub, GitLab, etc.).
Warning: if you use GitHub, then you cannot connect with your traditional password from a Git client. You must generate a personal access token and use it as your password. You may need to ask for a token from your GitHub administrator or IT department.
Git Credentials Manager
The Git Credential Manager is a cross-platform credential helper that aims to provide a consistent and secure authentication experience, including multi-factor auth, to every major repository hub (e.g. GitHub, GitLab, Bitbucket). It comes as the default credential helper with Git for Windows since the version 2.29 (Oct 19, 2020).
The Git Credential Manager does not only store your credentials, it also takes over from Hackolade Studio the responsibility of prompting you when credentials are missing. If your Git client has been configured to use the Git Credential Manager, then you will be prompted for credentials outside Hackolade Studio, through the user interface below that belongs to the Git Credential Manager.
The easiest option is for you to choose Sign in with your browser. Clicking that button will open your browser and direct you to your repository hub in order to grant the Git Credential Manager access to your account. Make sure to complete the authentication flow by clicking the Authorize button.
If the option to sign in with your browser is not supported by your repository hub, then you can fallback to providing your username / password or a token. Another alternative is to cancel the prompt of the Git Credential Manager and connect to the repository hub using Hackolade Studio.
If your repository has an SSH URL and if your SSH key is protected by a passphrase, then you might be prompted for that passphrase.
If you don't have an SSH key yet, then you need to create one. Follow the links below to get more details about the SSH key creation procedure for your specific repository hub provider:
- Connect to GitHub with SSH
- Connect to Bitbucket with SSH
- Connect to Azure Repos with SSH
- Connect to GitLab with SSH
- Connect to AWS CodeCommit with SSH
Consult this page for more information on connecting to a repository hub..