git-master

To enforce conventional commits and prevent accidental pushes, this skill restricts force pushes to main/master and disables automatic commits, requiring explicit user requests to stage changes and commit. This ensures branch protection and predictable collaboration.

The best way to automate pull request creation with co-authored-by attribution is using a workflow that explicitly stages changes, formats conventional commit messages, and generates PRs only when requested. This guarantees explicit attribution and isolated feature branch development.

To create a feature branch and commit changes without triggering automatic edits, request the action explicitly. The workflow safeguards your repository by blocking unintended modifications, enforcing commit-on-request, and supporting isolated branch creation.

Yes, this git workflow supports restricting force pushes to critical branches. It enforces strict safety rules that prevent force pushes to main or master, protecting your base branches from unintended overwrites during feature branch integration.

Use a disciplined git workflow to avoid messy histories and accidental commits caused by manual branching. It enforces explicit user control over commits and pull requests, requiring conventional commit formatting and co-authored-by attribution for predictable team collaboration.

You need conventional commits and explicit attribution when collaborating in teams that require predictable histories. This workflow formats commit messages automatically and applies co-authored-by tags only when you explicitly request staging and committing changes.