repo-release-tools 1.0.0

Config-driven branch and release helpers for Git repositories

repo-release-tools

repo-release-tools keeps release policy boring in the best possible way.

Use it from GitHub Marketplace when you want CI to validate branch names, commit subjects, and changelog policy. Install it from PyPI when you want a local CLI, hook integration, version bumps, and release-branch automation.

• GitHub Marketplace action: https://github.com/marketplace/actions/repo-release-tools-policy-checks
• PyPI package: https://pypi.org/project/repo-release-tools/

Choose your entry point

Use the GitHub Action for CI policy checks

Choose the action if you want pull requests and pushes to fail fast when a repo drifts from your release policy.

• validates branch names such as feat/add-parser
• validates Conventional Commit subjects
• validates changelog policy in CI
• optionally checks that the working tree stays clean
• can run rrt doctor as a pre-release health gate

- uses: actions/checkout@v6
  with:
    fetch-depth: 0

- uses: Anselmoo/repo-release-tools@v1.0.0
  with:
    check-branch-name: "true"
    check-commit-subject: "true"
    check-changelog: "true"

See the full action guide: https://github.com/Anselmoo/repo-release-tools/blob/main/docs/github-action.md

Use the Python package for local workflow automation

Choose the package if you want the developer-side tools: branch helpers, version bumps, config inspection, pre-commit hooks, and release automation.

pip install repo-release-tools
rrt init
rrt branch new feat "add parser"
rrt git commit "add parser"
rrt git doctor
rrt bump patch

Or run the CLI without installing it permanently:

uvx repo-release-tools branch new feat "add parser"

For basic versioning, bump and ci-version can run without [tool.rrt] by auto-detecting root-level pyproject.toml, package.json, and Cargo.toml. If multiple version files are found, they are updated together. Explicit config is for the nice extras: grouped releases, changelog paths, release branches, lock commands, generated files, and custom patterns.

Changelog workflows

The same project can be used in two release styles. Pick the one that matches how your repository actually lands changes.

Workflow	Best for	Hook behavior	Action changelog-strategy: auto	rrt bump default
incremental (default)	teams that maintain changelog entries during development	rrt-update-unreleased and rrt-changelog stay active	resolves to per-commit	auto
squash	repositories that squash many commits into one PR merge	changelog write/check hooks skip changelog enforcement	resolves to release-only	generate

Minimal config:

[tool.rrt]
release_branch = "release/v{version}"
changelog_file = "CHANGELOG.md"
changelog_workflow = "incremental"  # or "squash"

[[tool.rrt.version_targets]]
path = "pyproject.toml"
kind = "pep621"

Native config is also supported in package.json ("rrt": { ... }) and Cargo.toml ([package.metadata.rrt] / [workspace.metadata.rrt]). Go repos should use .rrt.toml or .config/rrt.toml.

What the project includes

• rrt CLI for branches, bumps, config inspection, and Git helpers
• rrt-hooks for pre-commit, lefthook, and CI validation
• a reusable GitHub Action in action.yml
• docs for branch policy, hook setup, and release workflows

Start with the doc that matches your task

• Docs index: https://github.com/Anselmoo/repo-release-tools/blob/main/docs/index.md
• GitHub Action: https://github.com/Anselmoo/repo-release-tools/blob/main/docs/github-action.md
• CLI reference: https://github.com/Anselmoo/repo-release-tools/blob/main/docs/rrt-cli.md
• Hook setup: https://github.com/Anselmoo/repo-release-tools/blob/main/docs/pre-commit.md
• Conventional branches: https://github.com/Anselmoo/repo-release-tools/blob/main/docs/semantic-branches.md
• Git workflow helpers: https://github.com/Anselmoo/repo-release-tools/blob/main/docs/git-magic.md
• Copilot skill: https://github.com/Anselmoo/repo-release-tools/blob/main/docs/skill.md

License

repo-release-tools is released under the MIT License.

Some workflow ideas were initially inspired by joseluisq/gitnow, but the rrt git surface is intentionally narrower and reshaped around conventional branching, safe commits, and release automation.

Built with ❤️ for safe, simple release automation.