Skip to main content
Configure custom git commit author identity across PraisonAI CLI commands and internal services.

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

Add to your shell profile (~/.bashrc, ~/.zshrc, ~/.bash_profile):
Reload your shell:

Affected Components

CLI Commands

The praisonai 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

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
Set team-wide defaults using environment management:
Different identities for different projects:

Best Practices

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
Add variables to your shell configuration for persistence:
This ensures the configuration persists across sessions.
Always verify your configuration before committing:
Use explicit parameters for special cases:

AI Commit

Generate AI-powered commit messages

Git Integration

PraisonAI git workflow integration