Loading...
Loading...
Create a pull request in a mitodl GitHub repository using the org's standard PR template. Triggered by /olpr or whenever the user asks to open a pull request in a repo whose remote is under the mitodl GitHub organization. Guides branch inspection, title/body population, and gh pr create invocation.
npx skill4agent add mitodl/agent-kit create-pull-request/olpr/olprmitodl/olprgithub.com/mitodl/git remote -v# Confirm current branch and its upstream
git --no-pager branch --show-current
git --no-pager log --oneline origin/HEAD..HEAD
# Check for an existing open PR on this branch
gh pr view --json url,title,state 2>/dev/nullmaingh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'| Field | How to obtain |
|---|---|
| Title | Ask the user, or suggest one derived from the branch name / commit messages |
| Linked tickets | Ask the user for issue numbers (Closes #, Fixes #, or N/A) |
| Description | Ask what the PR does; summarise from commits if the user says "summarise" |
| Screenshots | Ask if UI changes are present; skip section if not applicable |
| Testing notes | Ask how the changes were tested and how a reviewer can validate |
| Additional context | Ask for reviewer notes, caveats, or checklist items; skip if none |
| Draft? | Ask if this should be a draft PR (default: no) |
gh pr create### What are the relevant tickets?
<!-- Closes #<n> | Fixes #<n> | N/A -->
### Description (What does it do?)
<description>
### Screenshots (if appropriate):
<screenshot checklist, or delete section if not applicable>
### How can this be tested?
<testing instructions>
### Additional Context
<reviewer notes, or delete section if not applicable>### Checklist:
- [ ] <step>gh pr create \
--repo mitodl/<repo> \
--base <base-branch> \
--title "<title>" \
--body "<filled-in body>" \
[--draft]gh pr create### What are the relevant tickets?
<!--- If it fixes an open issue, please link to the issue here. -->
<!--- Closes # --->
<!--- Fixes # --->
<!--- N/A --->
### Description (What does it do?)
<!--- Describe your changes in detail -->
### Screenshots (if appropriate):
<!--- optional - delete if empty --->
- [ ] Desktop screenshots
- [ ] Mobile width screenshots
### How can this be tested?
<!---
Please describe in detail how your changes have been tested.
Include details of your testing environment, any set-up required
(e.g. data entry required for validation) and the tests you ran to
see how your change affects other areas of the code, etc.
Please also include instructions for how your reviewer can validate your changes.
--->
### Additional Context
<!--- optional - delete if empty --->
<!--- Please add any reviewer questions, details worth noting, etc. that will help in
assessing this change. --->
<!--- Uncomment and add steps to be completed before merging this PR if necessary
### Checklist:
- [ ] e.g. Update secret values in Vault before merging
--->git --no-pager log --oneline origin/HEAD..HEAD<!-- ... -->gh pr create--draft