ai-commit

Automated commit workflows stage changes, run linting via ruff, execute secret detection with gitleaks, and generate well-formed commit messages. This enforces security policies and project standards locally through git hooks, preventing non-compliant code from being committed.

Preventing secrets from being committed requires integrating gitleaks into your git hooks. The governed commit workflow automatically scans staged changes for secrets before committing, blocking any code that fails security policies from entering the repository.

Yes, ruff and gitleaks must be installed and available on the system PATH to automate the commit workflow. These dependencies are required to execute code formatting and secret detection checks locally before changes are committed.

Enforcing documentation updates before committing code is handled by a governed commit workflow. It checks that CHANGELOG.md and README.md are updated according to project standards, ensuring documentation remains current before changes are committed.

Yes, the governed commit workflow automatically creates feature branches for commits targeting protected branches. This branching strategy ensures changes are isolated before being committed and pushed.

If code fails formatting checks during an automated commit, the workflow stages all changes and automatically formats code using ruff. Non-compliant code that cannot meet security or project standards is prevented from being committed by local git hooks.