kata-contributing-pr

Creating a GitHub pull request with conventional commit titles requires analyzing your feature branch changes, validating commit history against repository rules, and applying mirrored issue labels. The workflow then generates a compliant PR using the correct template and metadata conventions.

Enforcing branch naming rules before opening a pull request involves validating your branch against the required `{type}/{issue-number}-{slug}` format. The process ensures your related issue is complete and your branch name matches contribution workflow standards before pushing to remote.

Automating issue label mirroring when creating a pull request happens after PR creation via GitHub MCP or gh CLI fallback. The workflow reads labels from the associated issue, applies them to the new PR, and stamps any additional PR-specific labels or cost directives required by the repository.

GitHub MCP is the preferred method for conventional commit PR workflows, with gh CLI available as a fallback. Both methods support creating standards-compliant pull requests by composing the PR title and body from the proper repository template and applying correct label conventions.

Pull requests fail repository contribution workflow checks when branch names do not match the `{type}/{issue-number}-{slug}` format, commit history violates conventions, or the PR body lacks the correct template. Final verification steps validate metadata, labels, and assignees before completion.

Validating commit history against repository rules before creating a PR is a core preparatory step. The process enumerates your commits, verifies they follow the required Lexis conventions, and checks repository status to ensure your contribution will be accepted smoothly.