anselmoo/repo-release-tools policy checks
Validate branch names, commit subjects, and changelog updates with repo-release-tools
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Jul 10, 2026
- License
- MIT
Pinned Snippet
uses: anselmoo/repo-release-tools@97b9ec7cb866903831cc9739167f531887bcdddc # v1.11.2tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| python-version | Python version used to run repo-release-tools | — | 3.12 |
| working-directory | Repository path to install and run repo-release-tools from | — | . |
| check-branch-name | Whether to validate the current branch name | — | true |
| branch-ref-type | Explicit ref type override for branch validation; defaults to the workflow ref type | no | — |
| branch-name | Explicit branch name to validate; defaults to the workflow branch | no | — |
| check-commit-subject | Whether to validate the commit subject | — | true |
| commit-subject | Explicit commit subject to validate; defaults to the latest commit subject | no | — |
| check-changelog | Whether to validate changelog updates for changelog-relevant commits | — | true |
| changelog-file | Explicit changelog path to validate | — | CHANGELOG.md |
| changelog-strategy | Changelog enforcement strategy: auto – (default) derive from changelog_workflow in repo config. incremental – alias for per-commit enforcement. per-commit – the changelog file must appear in the commit's changed-file list. unreleased – a non-empty [Unreleased] section must exist in the changelog. release-only – the check is skipped (changelog is updated only at release time). | — | auto |
| check-dirty-tree | Whether to fail when the checked-out work tree is dirty | — | false |
| check-doctor | Whether to run rrt doctor core automation checks. For historical release-target validation coverage, this also runs rrt release check unless explicitly disabled. | — | false |
| check-release-health | Whether to run rrt release check for version targets, pin targets, and changelog files | — | false |
| check-eol | Whether to check host runtimes and project minimums against end-of-life dates | — | false |
| check-docs | Whether to fail if source-owned docs have drifted from the lockfile. Detects source files added, modified, or deleted without regenerating .rrt/docs.lock.toml. | — | false |
| check-folder | Whether to validate the repository folder structure against [tool.rrt.folders] configuration. Fails on missing required files or directories. | — | false |
| check-artifacts | Whether to verify that generated artifact hashes match the committed .rrt/artifacts.lock.toml fingerprints. | — | false |
| verbose | Verbosity level for rrt-hooks output (0=quiet, 1=-v summary, 2=-vv details, 3=-vvv debug). Default: 0. | no | 0 |
Outputs
| name | description |
|---|---|
| detected-version | The current project version detected from the rrt configuration |
| changelog-status | Changelog status — one of 'clean', 'dirty', or 'missing' |
| health-summary | JSON object summarising the policy check results |