Which Git credential storage option stores your credentials only in memory for a limited time?
Think about a storage that forgets your password after some minutes.
The git-credential-cache stores credentials temporarily in memory, usually for 15 minutes by default. The others store credentials persistently or use external helpers.
What is the output of the following command if the credential store file does not exist yet?
git config --global credential.helper store cat ~/.git-credentials
Check what happens when you enable store but have not saved any credentials yet.
The credential.helper store saves credentials in ~/.git-credentials in plain text but does not create the file until credentials are saved. Initially, the file is empty or does not exist, so cat shows nothing.
You installed Git Credential Manager on Linux but Git still prompts for username and password every time. Which is the most likely cause?
Check if Git knows to use the credential manager.
If Git Credential Manager is installed but not set as the credential helper, Git will not use it and will prompt for credentials every time.
Which command correctly sets Git to cache credentials in memory for 10 minutes?
Remember the cache helper uses seconds for timeout.
The cache helper stores credentials in memory and accepts a --timeout option in seconds. 600 seconds equals 10 minutes.
You work on a shared workstation and want to store Git credentials securely without saving them in plain text files. Which credential helper is the best choice?
Consider helpers that integrate with OS secure storage.
git-credential-manager-core integrates with OS secure credential stores (like Windows Credential Manager, macOS Keychain, or Linux secret service), providing secure storage without plain text files. Cache stores in memory temporarily, store saves plain text files, and entering credentials every time is inconvenient.