gentle-ai-branch-pr

Automating Git branch naming and pull request creation requires enforcing an issue-first workflow, standardizing branch types like feature or fix, and linking PRs directly to approved issues. This ensures code maintainability and consistent commit history.

Enforcing Conventional Commits in a CI/CD workflow involves standardizing commit messages with specific prefixes like feat, fix, or chore, and integrating automated checks. This promotes a consistent and understandable project history across all contributions.

Linking a pull request to a GitHub issue automatically requires an issue-first development approach where branches are named using the issue number. The PR body is then generated to explicitly reference the corresponding approved issue.

Standardized Git branching workflows support multiple branch types including feature, fix, chore, docs, style, refactor, perf, test, build, ci, and revert. Each type enforces a clear naming convention for organized development.

Yes, the workflow requires an approved issue before creating a new feature branch. Issue-first enforcement guarantees that all pull requests are linked to a valid issue, ensuring code quality and maintainability.

Pull requests fail automated checks when they do not meet quality gates enforced by CI integration. Adhering to standardized branch naming, Conventional Commits, and linking to approved issues ensures PRs pass these required automated checks.