- review enablement
- severity thresholds
- base branch patterns
- ignored paths and title rules
How It Works
- Choose a source repository for centralized settings.
- Enable centralized config.
- Initialize the first sync in one of two modes:
prmode: Kodus creates an initialization PR with your current settings.manualmode: Kodus skips PR creation so your team can download configs and open the PR yourselves.
- After setup, centralized updates are synchronized automatically every time a PR is merged.
UI Workflow
From Settings > Code Review > General:- Open Centralized Config.
- Enable centralized config.
- Select the source repository.
- Pick Initial Sync Method:
- Automatic (Create PR now)
- Manual (Sync later)
- Save and confirm status.
Web UI Behavior When Enabled
When centralized config is enabled, repository settings become read-only in the web UI. The only settings users can still manage in the web UI are:- Kody Rules
- PR Messages
Sync Modes
- PR (default)
- Manual
Creates the initialization pull request automatically with your current
effective settings.
Download Configuration Bundle
You can download a ZIP bundle containing generated config files used for centralized setup and bootstrap. Use this when:- auditing generated configuration
- sharing setup artifacts with another team
- keeping a local backup for rollout
Disable Centralized Config
Disabling centralized config clears the selected source repository and returns repositories to non-centralized behavior. Use this only when you intentionally want to stop centralized propagation.CLI Dedicated Section
Use these commands to manage centralized config from terminal workflows and CI scripts.Requirements
- Team key authentication
- At least one selected repository in Kodus
Check Status
Initialize Centralized Config
--sync-optiondefaults topr.- If repository is omitted in an interactive terminal, CLI prompts selection.
- In non-interactive environments, repository must be provided.
Run Sync
Disable Centralized Config
Download Config ZIP
--outis required.- Output is a ZIP bundle containing generated config files.
JSON Output
All centralized commands support structured output with--json.
Related Docs
- CLI command reference: /how_to_use/en/cli/commands