Git Genius uses two authentication layers. Keeping them separate is intentional.
Used for:
- checking whether a GitHub repository exists
- creating a repository on GitHub
- validating the token and resolving the authenticated username
Sources:
- local Git Genius token storage at
~/.git-genius/token - environment variable
GIT_GENIUS_GITHUB_TOKEN
Environment-variable usage:
export GIT_GENIUS_GITHUB_TOKEN=your_token_here
git-geniusRecommended token scope:
repo
Used for:
git pushgit pull- any Git operation that talks to GitHub over HTTPS
This is separate from the GitHub API token storage above. Git itself still needs a credential helper if you want to avoid repeated prompts.
Configure it from:
Tools -> Git Auth / Credential Helper
Available modes:
- Memory cache
- recommended default
- keeps credentials for a limited time in memory
- does not write plaintext credentials to disk
- Persistent store
- saves credentials to
~/.git-credentials - survives restarts
- less secure because credentials are stored in plain text
- saves credentials to
After configuring a credential helper, Git Genius can preload the current GitHub token into Git.
This helps future HTTPS pushes stop prompting for:
- GitHub username
- GitHub token/password
For most local machines:
- Configure a GitHub token in Setup
- Open
Tools -> Git Auth / Credential Helper - Choose
Memory cache - Preload the GitHub credentials into Git
For automation-heavy environments:
- Export
GIT_GENIUS_GITHUB_TOKEN - Run Git Genius
- Optionally save the env token locally if you want interactive reuse
- Environment variables are good for automation and ephemeral sessions
- Memory cache is safer than persistent plain-text storage
- Persistent store is convenient but writes credentials to disk
- Git Genius never embeds the token in the remote URL