github-workflow

Automating GitHub pull requests and conventional commits is handled by creating conventional branches, staging specific files, and writing commit messages with safety rules to prevent secrets and unsafe commands. It uses the authenticated gh CLI to open PRs and link issues.

Linking a pull request to a GitHub issue requires using specific patterns like Fixes #N in the PR description. This workflow enforces linking PRs to issues during creation via the GitHub CLI to keep review and issue tracking consistent.

Using the authenticated gh CLI to manage git branching and code review is fully supported. It creates conventional branches from an up-to-date main branch, publishes updates, opens PRs, and coordinates review and merge activities automatically.

Running GitHub workflow automation requires both git and the authenticated gh CLI to be installed. These dependencies are necessary for executing branching, committing, pushing, and pull request tasks while enforcing workflow conventions.

Preventing force-pushing to protected branches during git workflows is enforced automatically by the system's safety guardrails. It enforces workflow conventions and avoids unsafe actions such as force-pushing to protected branches during commits and pushes.

Using conventional branches in your git workflow keeps work organized by separating feature, bugfix, and docs changes. It creates branches like feature/ or bugfix/ from an up-to-date main branch to maintain repository consistency.