machina-git

To ensure safe git commits across multiple repositories and submodules, use a centralized workflow gate that scans staged changes for secrets and evaluates commit readiness before allowing any git operation. This enforces atomic commits and reduces human error.

Secret scanning works by evaluating staged changes for commit readiness before executing a git commit. The workflow requires mandatory invocation before any git command, scanning the working directory for secrets and enforcing explicit user confirmation for destructive actions and pushes.

Yes, you can use conventional commits with a multi-repo git workflow. The workflow enforces conventional commit usage across all repositories and submodules, requiring you to cd into the target repository and run commands in a single shell invocation using logical chaining.

The best way to manage git submodules in a multi-repo workspace is to use a locked-down workflow that governs submodule updates alongside status, diff, add, commit, push, pull, branch, and tag operations, ensuring working directory safety and multi-repo consistency.

Your git workflow requires explicit confirmation before pushing to maintain an auditable workflow and prevent destructive actions. This centralized governance ensures all staged changes pass security and readiness checks, reducing human error across multiple repositories.

Yes, you need to cd into the target repository directory before running git commands. The workflow enforces working directory safety by requiring commands to be executed in the correct repository within a single shell invocation using logical chaining, such as cd repos/dem2 && git status.