Skip to content

Drafting a PR description

Unlike the explanations above, this is the one generation feature whose output is meant to be published — it fills a real template from the branch's per-file summaries and its commit list, the same range the branch explanation reads. The field stays a normal, editable textarea afterwards: nothing is submitted until you actually publish the PR.

Generating a PR description from a branch's commits

"Generate title and description (LLM)" reads everything the selected branch changes compared to its base — the whole range, not one commit — and writes a description from it, template included when the repo has one. Only the form is exercised here, not an actual PR submission: that reaches GitHub directly and is out of scope the same way the Launchpad's PR mutations are.

Generating a PR description from a branch's commits

Captured from the running app by this scenario.

Do this

  1. Check out the feature/login branch
  2. Open the create-PR form
  3. Fill the create-PR form with head feature/login and base main
  4. Click the generate-description button

You should see

  • The PR description field contains feat: add fake thing

This page is generated from apps/e2e/features/ai-pr-description.feature, the end-to-end test that drives the feature it describes.

MIT licensed · Screenshots exported from the real app by the end-to-end suite.