Running Git Pull, Commit, Push Without Re-authenticating (SSH, Credential)
This note summarizes the credentials (authentication) needed for Git operations.
Typically pull, commit, and push prompt for a user ID and password (or token); here we look at how to streamline that process.
[01] Ways to Store User Credentials in the Local Git
- Using an SSH key
- Generate an SSH key on the development machine and register it with Git.
- Use repositories via SSH.
- Using Git Config (Credential)
- Permanent storage on the system.
- Cache-based storage for a limited time.
[02] Register and Use an SSH Key
2-1. Generate an SSH Key
1
2
3
4
5
6
7
8
9
# Accept the defaults (Enter) for any prompts.
ssh-keygen -t rsa -C "Git" -b 4096
# Copy and paste the printed key into the SSH Key field on GitLab.
cat ~/.ssh/id_rsa.pub
# Sample output
root@cmaven:~# cat ~/.ssh/id_rsa.pub
ssh-rsa AAAA124123QABAAACAQCbKx1YXw8bUIWUb39eLkm7+AMVT92PhMCo...
2-2. Register the SSH Key with Git
Profile 
Settings SSH and GPG Keys New SSH Key Paste the key Add SSH Key
2-3. Clone the target repository over SSH
From this point onward, Pull/Commit/Push run without authentication prompts.
[03] Using Git Config (Credential)
- Run from the Git repository on the development machine.
- Apply one of the methods below and authenticate once with your ID and password (or token); subsequent Pull/Commit/Push operations run without re-authentication.
3-1. Permanent storage
1
2
3
4
git config credential.helper store
# verify changes
git config --list
3-2. Cache storage
1
2
3
4
5
# default 15 minutes
git config credential.helper cache
# specify time (timeout 3600 sec = 1 hour)
git config credential.helper `cache --timeout=3600`
3-3. Apply to all projects
1
git config credential.helper store --global