New Guide: Running BrassCoders on Every Commit
A new guide covers how to run BrassCoders on every commit — a CI step on push or a git pre-commit hook — and why there's no automatic watch mode. BrassCoders is a command-line scanner you invoke, not a background daemon.
BrassCoders now has a dedicated guide for one of the most common setup questions: how to run it on every commit. It leads with the part that trips people up, then gives copy-paste setup for both mechanisms.
Installing BrassCoders Doesn’t Make It Watch Your Commits
BrassCoders is a command-line scanner you invoke — it runs when a command runs it, and never on its own, because it has no background daemon or file watcher. BrassCoders removed its watch command and its monitoring module in version 2.0.9, so continuous background scanning isn’t a mode it offers. “On every commit” is a cadence you wire up, in one of two places: a CI step on push, or a git pre-commit hook.
That distinction is the thing people get wrong — they expect a resident watcher and there isn’t one. The guide leads with it before any configuration, so the mental model is right before the YAML shows up.
What the New Guide Covers
BrassCoders’s new guide walks through both mechanisms end to end — a CI step on push (GitHub Actions and GitLab CI) and a git pre-commit hook — plus --offline for zero-egress local hooks and how the exit code turns a scan into a build gate.
Read it here: Running BrassCoders on Every Commit. For the broader pre-commit-plus-CI-plus-merge-gate architecture with an audit trail, it cross-links the CI/CD Code Gates guide.
Install and try a scan in under two minutes:
pip install brasscoders
brasscoders --offline scan /path/to/your/projectFrequently Asked Questions
Does BrassCoders run automatically on every commit?
No. BrassCoders is a command-line scanner you invoke with `brasscoders scan`. It has no background daemon or file watcher, so it runs only when a CI step or a git hook runs it. Scanning on every commit becomes true once you wire BrassCoders into CI on push or a pre-commit hook.
Does BrassCoders have a watch or daemon mode?
No. BrassCoders removed its `watch` command and monitoring module in version 2.0.9. BrassCoders is a single-invocation CLI by design: it scans, writes YAML to `.brass/`, and exits. Continuous background scanning is not a feature it offers.
Where is the full setup for CI and pre-commit hooks?
The guide Running BrassCoders on Every Commit at coppersun.dev/run-on-every-commit/ has copy-paste configuration for a GitHub Actions step, a GitLab CI step, and a git pre-commit hook, plus how the exit code gates the build. It's the canonical how-to for the on-every-commit cadence.