Changing Language
Use thechange-language command to set your preferred language:
Supported Languages
GitWhisper supports the following languages:English
- English (US)
- English (UK)
European
- Spanish
- French
- German
- Italian
- Portuguese
- Russian
- Dutch
- Swedish
- Norwegian
- Danish
- Finnish
- Greek
Asian
- Chinese (Simplified)
- Chinese (Traditional)
- Japanese
- Korean
- Hindi
Middle Eastern
- Arabic
- Turkish
African
- Shona
- Zulu
Language Configuration
The language setting is stored in your configuration file (~/.git_whisper.yaml):
language_code;country_code:
en;US- English (United States)en;GB- English (United Kingdom)es;ES- Spanish (Spain)fr;FR- French (France)de;DE- German (Germany)zh;CN- Chinese (Simplified, China)zh;TW- Chinese (Traditional, Taiwan)ja;JP- Japanese (Japan)ko;KR- Korean (Korea)ar;SA- Arabic (Saudi Arabia)sn;ZW- Shona (Zimbabwe)zu;ZA- Zulu (South Africa)
Commit Message Examples
Here’s how commit messages appear in different languages:Conventional Commit Prefixes
GitWhisper follows the Conventional Commits specification. The prefixes remain in English for compatibility with tools and parsers:feat:- New featurefix:- Bug fixdocs:- Documentation changesstyle:- Code style changes (formatting, etc.)refactor:- Code refactoringtest:- Adding or updating testschore:- Maintenance tasksperf:- Performance improvementsci:- CI/CD changesbuild:- Build system changes
While the commit type prefixes remain in English, the commit message description and body will be in your configured language.
How It Works
When you generate a commit message:- GitWhisper analyzes your staged changes
- Sends the changes to the AI model with your language preference
- The AI generates a commit message in your specified language
- Conventional commit prefixes remain in English
- The description and body are in your configured language
Best Practices
Choosing a language for your team
Choosing a language for your team
Consider your team’s composition:
- International teams: Use English as the common language
- Regional teams: Use the local language for better communication
- Open source projects: English is recommended for wider accessibility
- Private projects: Use whatever language your team is most comfortable with
- Use code review to enforce:
- Check that commit messages are in the agreed language
- Request changes if messages are in a different language
Multilingual projects
Multilingual projects
For projects with international contributors:
- Stick with English for maximum compatibility
- Document this requirement clearly in your README
- Consider that tools and CI/CD systems may expect English
Impact on commit history searchability
Impact on commit history searchability
Consider how language affects searching:English commits:Spanish commits:Tips:
- Document common search terms in your project wiki
- Consider creating aliases for frequently searched terms
- Use issue/ticket numbers in commits for language-agnostic searching:
CI/CD and tooling compatibility
CI/CD and tooling compatibility
Most CI/CD tools expect English:
- Semantic release tools often parse English keywords
- Changelog generators may not understand non-English messages
- Some git hooks might validate against English patterns
- Verify your tooling supports it
- You may need to customize parsers and validators
- Consider using English for automated commits (CI/CD) and your language for manual commits
Viewing Current Language
Check your current language configuration:Configuration File
The language setting is part of your~/.git_whisper.yaml:
Changing Language Manually
While thechange-language command is recommended, you can manually edit the configuration file:
Language-Specific Features
Date Formats
Dates in commit messages follow regional formats:- en;US: 12/31/2025 (MM/DD/YYYY)
- en;GB: 31/12/2025 (DD/MM/YYYY)
- ja;JP: 2025年12月31日
- zh;CN: 2025-12-31
Number Formats
Numbers may be formatted according to regional conventions:- en;US: 1,000.50
- de;DE: 1.000,50
- fr;FR: 1 000,50
Fallback Behavior
If the language is not set or invalid:- GitWhisper defaults to
en;US(English, United States) - A message is logged: “Using default language: English”
- No error is thrown - the commit proceeds with English messages
Code Analysis Language
The language setting also affects code analysis output:Troubleshooting
Language not changing
Language not changing
- Verify the configuration was saved:
- Check file permissions on
~/.git_whisper.yaml - Try running
change-languageagain - Restart your terminal session
Mixed language commits in history
Mixed language commits in history
If your commit history has mixed languages:
- This is normal when changing language settings
- Old commits retain their original language
- New commits will use the new language
- To standardize, you would need to rewrite history (not recommended)
AI generates wrong language
AI generates wrong language
If the AI generates commits in a different language:
- Verify your language configuration:
- Check that the format is correct:
language_code;country_code - Some AI models might occasionally slip into another language - regenerate:
- Try a different model that has better multilingual support
Special characters not displaying
Special characters not displaying
If you see garbled text or boxes instead of characters:
- Ensure your terminal supports UTF-8:
- On Windows, use Windows Terminal or a UTF-8 compatible terminal
- Configure your git to use UTF-8:
Regional Variants
Some languages have regional variants:English
en;US- American English (color, analyze)en;GB- British English (colour, analyse)
Chinese
zh;CN- Simplified Chinese (简体中文)zh;TW- Traditional Chinese (繁體中文)
Next Steps
API Keys
Learn how to manage API keys for different providers
Default Settings
Configure default model and behavior preferences
Usage Guide
Start using GitWhisper with your configured language
Advanced Features
Explore advanced language-specific features