Skip to main content

Issue To Pull Request Walkthrough

Use this walkthrough when you want ProPR to turn a GitHub issue into a pull request.

This is one stage of ProPR, and it stands on its own. The issue you start from can be written by hand, produced by another planning tool, or generated by Planner Studio — ProPR does not need to have planned it.

After setup, adding the processing label is the only thing required to start implementation. That makes "issue implementation only" a complete way to use ProPR.

Before You Start​

Make sure:

  • Setup is complete.
  • The repository is configured in the Web UI.
  • An AI Agent and default model are enabled.
  • The issue is clear enough to implement.
  • You know the processing label for the repository, such as AI or propr.

Prepare The Issue​

Write the issue for implementation:

  • What should change
  • Why it should change
  • Acceptance criteria
  • Relevant screenshots or links
  • Anything out of scope

Small, specific issues produce better PRs than broad requests.

Start The Run​

  1. Add the processing label to the issue (for example AI).
  2. Optionally add a model label such as llm-claude-opus5 or llm-antigravity-pro. Adding several model labels produces one run, branch, and PR per model.
  3. Optionally add base-<branch> (for example base-develop) to target a non-default base branch.
  4. Open the ProPR Web UI.
  5. Watch the task record.

ProPR picks up the label through its configured event intake mode — by default it receives the event near-immediately over the routing WebSocket; with GITHUB_EVENT_INTAKE_MODE=polling it is detected on the next polling cycle (every 60 seconds by default), and with direct_webhook it arrives as GitHub delivers it. As the run progresses, ProPR adds state labels alongside the trigger label: <trigger>-processing while running, then <trigger>-done on success or a <trigger>-failed-* label on failure.

The task record shows the selected repository, branch, model, status, logs, and resulting PR.

Review The Pull Request​

When ProPR opens the PR:

  • Read the summary. The PR body links the source issue with Closes #N, so merging closes the issue automatically.
  • Review the diff.
  • Check tests and CI.
  • Confirm the change matches the issue.
  • Look at the task record if anything is unclear.

Review the PR in your normal process. ProPR helps create and refine it — merging the PR remains a human decision.

Ask For Follow-Up​

A plain PR comment such as Please add a regression test for the empty state. initiates a follow-up run once the PR carries a processing label (or the comment includes a configured trigger keyword) — this works on PRs opened outside ProPR too. Slash commands cover specific actions: /review posts a read-only AI review, /fix applies the pending suggestions a /review produced, and /merge merges the base branch into the PR branch. Daily Use → Refine A Pull Request covers the full command list and PR takeover; PR Slash Commands is the reference.

Recover Or Re-Run​

If the run fails:

  1. Open the task record.
  2. Read the failure message and logs.
  3. Check the <trigger>-failed-* label on the issue for the failure category.
  4. Check credentials, branch settings, and agent configuration.
  5. Add clearer PR or issue instructions if needed.
  6. Re-run with a smaller scope or different model.

Related pages: