Available Commands
gleef init
Initialize Gleef in your project by detecting locale files and creating configuration
gleef login
Authenticate with Gleef using your API key
gleef translate
Push translation keys to Gleef for AI-powered translation
gleef push
Push translation changes to Gleef without AI translation
gleef pull
Get the latest translations from Gleef and update local files
Command Reference
Core Commands
| Command | Purpose | When to Use |
|---|---|---|
gleef init | Project setup | First time setting up Gleef in a project |
gleef login | Authentication | When setting up CLI or changing API keys |
gleef translate | AI-powered translation | When you have new keys that need AI translation |
gleef push | Push changes only | When you want to upload manual edits without AI translation |
gleef pull | Sync translations | When you want to get latest translations from your team |
Global Flags
All commands support these global flags:| Flag | Description |
|---|---|
--help | Show help information for the command |
--version | Display the CLI version |
Getting Help
Get help for any command using the--help flag:
Command Workflow
Here’s the typical workflow using Gleef CLI commands:1
Initial Setup
2
Push New Content
3
Sync Updates
4
Ongoing Development
Command Examples
Basic Usage
Advanced Usage
Error Handling
All commands provide clear error messages and exit codes:- Exit code 0: Command completed successfully
- Exit code 1: Command failed with an error
- Authentication errors: Run
gleef loginto re-authenticate - Configuration errors: Check your
.gleef/config.jsonfile - Network errors: Verify your internet connection and API access
- File errors: Ensure your locale files are properly formatted