Skip to content

Add a PR template with a required "How to verify" section#360

Draft
MichaelLeeHobbs wants to merge 1 commit into
OpenIntegrationEngine:mainfrom
MichaelLeeHobbs:feature/pr-template-how-to-verify
Draft

Add a PR template with a required "How to verify" section#360
MichaelLeeHobbs wants to merge 1 commit into
OpenIntegrationEngine:mainfrom
MichaelLeeHobbs:feature/pr-template-how-to-verify

Conversation

@MichaelLeeHobbs

Copy link
Copy Markdown

What & why

Adds .github/PULL_REQUEST_TEMPLATE.md — the repo had none. Its centerpiece is a required How to verify section, so a PR ships with a reviewer-runnable before/after instead of just "tests pass." Short checklist mirrors CONTRIBUTING and the AGENTS.md contributor guardrails (one concern, fail-before/pass-after test, the exact local build command, behavior/compat, no PHI/unsafe-deserialization).

Closes #359. Origin: @pacmano1's request during review of #343 — the mechanic who replaces the battery but never starts the car. Also closes the gap where CONTRIBUTING asks bug reports for repro + expected-vs-actual but asks PRs only for "a brief description."

How to verify

N/A — no runtime/behavior change; this is a GitHub meta file. To confirm it takes effect:

  • On this branch the file renders: .github/PULL_REQUEST_TEMPLATE.md.
  • After merge, opening a new PR pre-fills it (GitHub picks up the template automatically).
  • This PR itself follows the template it introduces — references an issue and fills in What/why + this section.

Checklist

  • Scoped to one concern (adds one file)
  • N/A — no code/tests (docs/meta)
  • N/A — no build impact
  • N/A — no behavior/compat surface
  • No PHI / deserialization surface

The repo has no PR template, and CONTRIBUTING asks a PR only for 'a brief
description' while asking bug *reports* for steps-to-reproduce and
expected-vs-actual. So a bug report is held to a higher reproducibility bar
than the fix for it.

This closes that gap: a required How to verify section asking for a
reviewer-runnable before/after (and exact steps + observed result for
behavior a unit test can't show), plus a short checklist mirroring
CONTRIBUTING and the AGENTS.md contributor rules. Reviewers get a way to
turn the key instead of trusting green CI.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add a PR template with a required "How to verify" section

1 participant