Github Auth — GitHub auth setup: HTTPS tokens, SSH keys, gh CLI login
Github Auth — GitHub auth setup: HTTPS tokens, SSH keys, gh CLI login
Start with meaning, then move to detail.
This lesson explains Github Auth — GitHub auth setup: HTTPS tokens, SSH keys, gh CLI login as part of getting started with Hermes correctly. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Skill metadata, Reference: full SKILL.md, Detection Flow, then verify failure modes and version compatibility.
No prior experience is required; follow the steps on a safe test setup first.
A clear outcome before you read.
- Understand Github Auth — GitHub auth setup: HTTPS tokens, SSH keys, gh CLI login without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Skill
- An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
- Browser / CDP
- A layer for programmatic browser control and page or event inspection.
GitHub auth setup: HTTPS tokens, SSH keys, gh CLI login
What does the source say, and in what order?
- 01Skill metadata
Start here to understand the core idea or structure.
- 02Reference: full SKILL.md
Read this after the foundation, then connect it to the previous step.
- 03Detection Flow
Read this after the foundation, then connect it to the previous step.
- 04Method 1: Git-Only Authentication (No gh, No sudo)
Read this after the foundation, then connect it to the previous step.
- 05Option A: HTTPS with Personal Access Token (Recommended)
Read this after the foundation, then connect it to the previous step.
- 06Option B: SSH Key Authentication
Read this after the foundation, then connect it to the previous step.
- 07Method 2: gh CLI Authentication
Read this after the foundation, then connect it to the previous step.
- 08Interactive Browser Login (Desktop)
Read this after the foundation, then connect it to the previous step.
- 09Token-Based Login (Headless / SSH Servers)
Read this after the foundation, then connect it to the previous step.
- 10Verify
Finish here to verify the result and special cases.
Copy only after you understand the effect.
# Check what's available
git --version
gh --version 2>/dev/null || echo "gh not installed"
# Check if already authenticated
gh auth status 2>/dev/null || echo "gh not authenticated"
git config --global credential.helper 2>/dev/null || echo "no git credential helper"# Set up the credential helper to cache credentials
# "store" saves to ~/.git-credentials in plaintext (simple, persistent)
git config --global credential.helper store
# Now do a test operation that triggers auth — git will prompt for credentials
# Username: <their-github-username>
# Password: <paste the personal access token, NOT their GitHub password>
git ls-remote https://github.com/<their-username>/<any-repo>.git# Cache in memory for 8 hours (28800 seconds) instead of saving to disk
git config --global credential.helper 'cache --timeout=28800'Read the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.