pr
- Repo stars 357
- Author repo woocommerce-ios
- Domain
- Engineering
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @woocommerce · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
Create a pull request following WooCommerce iOS conventions.
Steps:
1. Verify the current branch is not `trunk`:
```bash
git branch --show-current
```
2. Check the diff against trunk:
```bash
git log trunk..HEAD --oneline
git diff trunk...HEAD --stat
```
3. Check non-test diff size (should be under 300 lines):
```bash
git diff trunk...HEAD --stat -- . ':!*Tests*' ':!*Test*' ':!*.generated.*'
```
4. Review the changes to write an accurate description. Read modified files if needed.
- **Never include actual Linear issue links** (e.g., `https://linear.app/...`) in PR descriptions — Linear is an internal resource. Only reference the issue ID (e.g., `WOOMOB-2485`).
5. Determine if RELEASE-NOTES.txt needs updating. If the change is user-facing, remind about adding a release note entry.
6. Push the branch:
```bash
git push -u origin HEAD
```
7. Create the PR. The description must follow the template in `.github/PULL_REQUEST_TEMPLATE.md`:
```bash
gh pr create --base trunk --title "<concise title>" --body "$(cat <<'EOF'
## Description
<description of changes — why and what>
## Test Steps
<how to test>
## Screenshots
N/A
---
- [ ] I have considered if this change warrants user-facing release notes and have added them to `RELEASE-NOTES.txt` if necessary.
EOF
)"
```
8. **Add labels.** After creating the PR, add all labels in a single call using multiple `--add-label` flags: `gh pr edit <number> --add-label "<label1>" --add-label "<label2>"`. Pick labels from these categories:
- **Type** (pick one): `type: bug`, `type: crash`, `type: enhancement`, `type: task`, `type: technical debt`, `type: documentation`, `type: question`
- **Feature** (pick one if applicable): match the changed area to a `feature: *` label (e.g., `feature: POS`, `feature: order list`, `feature: order details`, `feature: product details`, `feature: login`, `feature: dashboard`, `feature: analytics hub`, `feature: coupons`, `feature: shipping labels`, `feature: order creation`, `feature: notifications`, `feature: Blaze`, `feature: CIAB Mobile Experience`, `feature: subscriptions`, `feature: app settings`, etc.)
- **Priority** (pick one if known): `priority: low`, `priority: medium`, `priority: high`, `priority: critical`
- **Category** (pick any that apply): `category: accessibility`, `category: design`, `category: performance`, `category: tracks`, `category: unit tests`, `category: ui tests`, `category: tooling`, `category: parity`, `category: i18n`, `category: dark mode`, `category: tablet`, etc.
- If the feature is behind a flag, also add `status: feature-flagged`
- Infer labels from the diff and branch name. If unsure about the feature label, ask the user.
9. **Set milestone.** After creating the PR, assign the correct milestone:
- List open milestones: `gh api repos/woocommerce/woocommerce-ios/milestones --jq '.[] | "\(.title)\t\(.description)"'`
- Each milestone description contains a `Code Freeze:` date.
- **If the PR targets `trunk`**: pick the earliest milestone whose code freeze date has **not yet passed** (i.e., the next unfrozen milestone).
- **If the PR targets a `release/X.Y` branch**: use milestone `X.Y` (the frozen release milestone).
- Apply with: `gh pr edit <number> --milestone "<milestone title>"`
10. Report the PR URL.
If non-test diff exceeds 300 lines, warn that Danger will flag it and suggest splitting.
Sections and files
Listed in source order.
sections -> → → → → →
terms -> Never include actual Linear issue links · Add labels. · Type · Feature · Priority · Category · Set milestone. · If the PR targets trunk
files/cmd -> trunk · https://linear.app/... · WOOMOB-2485 · .github/PULL_REQUEST_TEMPLATE.md · RELEASE-NOTES.txt · --add-label · gh pr edit <number> --add-label "<label1>" --add-label "<label2>" · type: bug
body sha256 -> 71c03b992e07
Create a pull request following WooCommerce iOS conventions.
Steps:
Verify the current branch is not
trunk:Check the diff against trunk:
Check non-test diff size (should be under 300 lines):