integrationIntegrate git-agent's commit validation into your CircleCI pipeline
CircleCI is a cloud-native CI/CD platform with fast build times, caching, and fine-grained pipeline control. By adding a git-agent validation step to your CircleCI config, you can enforce Conventional Commits compliance, block non-conforming merges, and trigger semantic releases — all in a single .circleci/config.yml pipeline. CircleCI's orb ecosystem makes it straightforward to create reusable commit validation jobs that run on every push or pull request.
Benefits
- Enforce commit message conventions across all branches and forks in a single pipeline
- CircleCI parallelism and caching reduce validation overhead per commit
- Orb-based configuration makes it easy to share git-agent validation across repos
- Block merge on non-conventional commits with status checks in the GitHub/GitLab integration
Setup steps
- Install git-agent locally for local development and testing
- Create a .circleci/config.yml with a validate-commits job that runs on workflow dispatch
- Use the CircleCI CLI to validate the config locally before pushing
- Set up branch protection rules that require the git-agent validation job to pass before merging
FAQ
Can I use CircleCI with git-agent's free shared gateway?Yes. The free shared gateway is the default and requires no configuration. For CI environments, git-agent's CLI can be installed as part of the build step.
Does CircleCI support git-agent on all execution environments?Yes. git-agent's Go binary runs on Linux, macOS, and Windows. CircleCI's Docker, machine, and macOS executors all support it.
Can I use CircleCI orbs to share git-agent validation across multiple repositories?Yes. You can create a custom orb that wraps git-agent's validation commands, or use an existing conventional-commit orb. This keeps your CI config DRY across projects.