Skip to content

Latest commit

 

History

History
41 lines (30 loc) · 2.69 KB

README.md

File metadata and controls

41 lines (30 loc) · 2.69 KB

Documentation

Project README

Pick up where you are

What you want to do GitHub Azure DevOps
Copy existing keys into CI or configure automation Setup and key commands Setup and key commands
Choose branch protections and allowed mergers Rulesets: solo/team presets —
Configure merge-commit title and description Settings and screenshots —
Apply the PR-only/history baseline with the CLI Two-ruleset recipe —
Use a compact returning-user checklist Quickstart Quickstart
Follow a complete release and hotfix process Choose your guide Choose your guide

Already have keys? The setup pages, quickstarts, and complete guides each include the commands and exact secret names. You do not need to start from scratch or create new keys.

First time? Install the CLI, choose a complete guide, and follow its numbered steps. Missing SSH/GPG keys have optional creation steps in platform setup. Configure an LLM provider only if you want AI-generated commit or PR text; versioning CI needs no LLM key.

Each complete guide now contains both the worked lifecycle and its mode policy. There is no separate mode-reference page to assemble. Reviewed modes use their base flow's adapter: enable one versioning workflow/pipeline per application.

Local commands and reference

Guide Use it for
CLI usage Commands, options, defaults, and interactive operation
Configuration Providers, credentials, models, and saved settings
Versioning .cz.toml, best-effort Python/Node/Rust sync, and custom targets
Flow comparison Choosing classic or release-led, reviewed modes, and shared title rules
Publication Failed CI publication and missing-tag recovery
DVC Optional manual data and experiment workflow

Before sending repository content to a provider, read the configuration limitations. Before custom version selectors or bump planning, read the versioning limitations.

Project maintenance