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.
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..