pm-pr-workflow

Git branch protection is enforced by automatically checking user permissions based on their email address and routing non-privileged users away from direct main branch commits. This mechanism intercepts invalid pushes and requires a feature branch and pull request instead.

To create a pull request, the workflow delegates to a version-control agent using a structured template that captures task parameters. It requires you to provide a work summary, a list of changed files, and the current test status to ensure complete context for code review.

When a direct push to the main branch is attempted without permissions, the workflow intercepts the action and explains that branch protection rules require a pull request. It then guides the developer through creating a feature branch and submitting a PR for review.

Automated workflow routing intelligently guides users towards feature branch creation for non-privileged operations. It manages routing rules based on user email to ensure all non-privileged changes follow the correct version control path before merging.

Yes, routing rules for direct main branch access are managed based on user email, allowing specific privileged users to bypass the pull request workflow. All other users are automatically enforced to use feature branches and pull requests.

A structured template for pull request creation ensures all necessary context is included for code review. It enforces the inclusion of a work summary, file lists, and test status, which prevents common Git errors and maintains code quality.