Quick Start
1
Set Environment Variables
Configure your git identity using environment variables:
2
Use GitHub Noreply Email
Protect your personal email on GitHub:
3
Test Configuration
Verify the configuration works:
How It Works
PraisonAI reads identity configuration in this priority order:Environment Variables
Default email varies by service:
- CLI commands: No default (uses global git config)
- CheckpointService:
"checkpoints@praison.ai" - FileSnapshot:
"praison@snapshot.local"
Setup Methods
- Shell Configuration
- Session Only
- Project Specific
Add to your shell profile (Reload your shell:
~/.bashrc, ~/.zshrc, ~/.bash_profile):Affected Components
CLI Commands
Thepraisonai commit command uses the environment variables for git author:
Checkpoint Service
Internal checkpoints use the configured identity:File Snapshot
File snapshots use the configured identity:Common Patterns
GitHub Integration
GitHub Integration
Using GitHub noreply email for privacy:This ensures:
- Commits are attributed to your GitHub account
- Your personal email is not exposed
- GitHub shows your profile picture and username
Team Environment
Team Environment
Set team-wide defaults using environment management:
Multi-Project Setup
Multi-Project Setup
Different identities for different projects:
Best Practices
Use GitHub Noreply Email
Use GitHub Noreply Email
Always use GitHub’s noreply email format to protect your privacy:Benefits:
- Commits link to your GitHub profile
- Personal email stays private
- Works with all GitHub features
Set in Shell Profile
Set in Shell Profile
Add variables to your shell configuration for persistence:This ensures the configuration persists across sessions.
Verify Configuration
Verify Configuration
Always verify your configuration before committing:
Override When Needed
Override When Needed
Use explicit parameters for special cases:
Related
AI Commit
Generate AI-powered commit messages
Git Integration
PraisonAI git workflow integration

