create-pr

Automating GitHub pull request creation with conventional commits involves generating structured PR titles and bodies that include a type, scope, and Jira reference. This standardizes changes across repositories to reduce review time and inconsistencies.

To link a Jira ticket to a GitHub PR body automatically, the pull request generation process extracts the ticket reference and embeds it within the PR body alongside a summary and checklist, ensuring reviewers can quickly track the associated task.

Yes, you can generate a draft PR using conventional commit formatting. The automation process supports choosing between regular pull requests and draft PRs while applying the required type and scope structure to the title.

The correct scope for conventional commit titles in multi-project repositories is determined by predefined project identifiers such as vue, dotnet, pedidos, or api. This targeted scoping ensures changes are correctly categorized for each specific codebase.

Yes, PR automation detects the correct base branch automatically. It identifies current changes and verifies the target branch before creating the pull request, guiding the user through the necessary verification steps to ensure accurate merging.

Using conventional commits for pull request titles enforces a standardized format like feat(vue): add feature, which clarifies the change type and scope. This structure reduces review time and eliminates inconsistencies across multiple development projects.