git-conventions

To enforce safe git conventions, apply standardized rules across commit, push, and branch workflows to prevent risky commands and nondeterministic histories. These rules integrate directly into pre-commit hooks and CI pipelines for automatic compliance.

Prohibited git operations include force-push, unverified commits, and bypassing pre-commit hooks. Additionally, avoid using git -C path hacks and ensure standard commands execute directly in the working directory to maintain history integrity.

No special dependencies are required to set up pre-commit hooks for git workflows. You only need standard Git and shell tooling already available in your environment to integrate and enforce these safety conventions locally or in CI.

You should avoid the git -C path option because it creates hidden execution contexts that bypass standard workflow safety. Enforcing direct execution in the repository root ensures transparent git status and git diff checks before committing.

The best way to standardize git commit and push rules in CI pipelines is by codifying a repeatable set of safe git rules and invoking them as part of the pipeline to enforce policy conformance automatically across all repositories.