docs: add pull request template#419
Conversation
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
LGTM — docs-only addition of a PR template.
Extended reasoning...
Overview
This PR adds a single new file, .github/pull_request_template.md, which GitHub will use to pre-populate the body for new pull requests. No code, build, CI, or test logic is touched.
Security risks
None. The file is markdown content used solely as a UI scaffold in the GitHub web/PR creation flow. It contains no executable code, no secrets, and no references to credentials or infrastructure.
Level of scrutiny
Minimal scrutiny is appropriate. This is a non-code documentation change with effectively zero blast radius — it only affects the default text shown when opening a new PR, and contributors can freely edit or delete sections in their PR body. The template's content mirrors the structure already used in recent PRs (e.g., #418), as the description notes.
Other factors
The timeline shows no prior reviews or outstanding comments. The bug hunting system found no issues. This is exactly the type of mechanical, low-risk change suitable for shadow approval.
Adds a .github/pull_request_template.md so new PRs come pre-populated with the sections we already use in practice (summary, motivation with Linear link, scope, testing, affected code checklist).
sherwinski
force-pushed
the
sherwin/add-pr-template
branch
from
ad6c4f2 to
826a8b5
Compare
There was a problem hiding this comment.
LGTM, straightforward addition of a PR template.
Extended reasoning...
Overview
This PR adds a single new file, .github/pull_request_template.md, which GitHub uses to pre-populate the body of new PRs in this repo. The template codifies the structure recent PRs have followed (One Line Summary, Motivation, Scope, Testing, checklists).
Security risks
None. This is a documentation-only change with no executable code, no CI hooks, and no impact on the plugin runtime, build, or release pipeline.
Level of scrutiny
Minimal scrutiny warranted. A PR template is purely informational — it cannot break anything, and the contents are reasonable and consistent with the project's existing conventions.
Other factors
The bug hunting system found no issues. The change is self-contained (one new file), the markdown is well-formed, and the description clearly explains the motivation. Safe to approve without human review.
2 participants
One Line Summary
Add
.github/pull_request_template.mdso new PRs come pre-populated with the sections we already write by hand.Motivation
Recent PRs (e.g. #418) have followed a consistent structure — One Line Summary, Motivation with Linear link, Scope, Testing, Affected code checklist. Codifying that as the GitHub PR template removes the cognitive load of remembering the format and gives external contributors a clear pattern to follow.
Scope
.github/pull_request_template.md(new file). GitHub will use it as the default PR body for new PRs in this repo.Testing
Affected code checklist
v3/)Checklist