// Push the current branch and create a pull request on tikv/pd following the repository's PR template. Analyzes commits, generates PR title/body from changes, and submits via `gh pr create`. Use when you have local commits ready to submit as a PR.
Use when a problem, task, or idea needs to be tracked as a GitHub issue on tikv/pd. Searches for duplicates, picks the right issue template, drafts the title and body, shows the draft for user approval, and submits via `gh issue create`.
Repair cherry-pick pull requests in tikv/pd when automated cherry-picks leave committed conflict markers, drift from the source PR, or need parity verification against the original PR. Use when given a source PD PR and its cherry-pick PR, or a cherry-pick PR that references an original PR, and asked to compare diffs, resolve release-branch cherry-pick conflicts, run failpoint-aware verification, and push the fixed cherry-pick branch.
Add or change Prometheus metrics — cache WithLabelValues, hot path, cleanup, avoid high cardinality, naming, MustRegister, backward compatibility. From tikv/pd metrics PRs.
| name | create-pr |
| description | Push the current branch and create a pull request on tikv/pd following the repository's PR template. Analyzes commits, generates PR title/body from changes, and submits via `gh pr create`. Use when you have local commits ready to submit as a PR. |
| compatibility | Requires gh CLI authenticated with tikv/pd repo access. Must have local commits on a non-master branch. |
PD contributor assistant. Push the current branch and open a well-formatted pull request on tikv/pd, auto-filling every section of the PR template based on the actual changes.
| File | Contents | Load When |
|---|---|---|
.github/pull_request_template.md | The exact PR template structure | Phase 2 — when composing the PR body |
| references/pr-template.md | Additional filling guidelines for the PR template | Phase 2 — when composing the PR body |
Collect all information needed to fill the PR template. Run these in parallel:
git status — confirm working tree is clean (no uncommitted changes).git branch --show-current — get current branch name.git log --oneline master..HEAD — list all commits being submitted.git diff master...HEAD --stat — summary of changed files.git diff master...HEAD — full diff for analysis.Gate: If working tree is dirty, ask the user whether to commit first or proceed with committed changes only. If on master, stop and ask the user to create a branch.
Load
.github/pull_request_template.mdand references/pr-template.md now.
references/pr-template.md, compose the PR title and fill every section of the PR body template.After user approval:
Push the branch:
git push -u origin <branch-name>
Create the PR:
gh pr create --repo tikv/pd --title "<title>" --body "<body>"
Use a HEREDOC for the body to preserve formatting.
Report the PR URL back to the user.
If the push or PR creation fails:
gh auth login.gh CLI for GitHub operations. Do not guess API URLs.pkg: message format for title.