docs: add pull request template#86
Merged
Merged
Conversation
Adds .github/PULL_REQUEST_TEMPLATE.md with the sections requested in lujax-dev#80: description, related issue, type of change, testing notes and a short checklist (tests, lint, docs). Kept deliberately brief to lower friction for new contributors rather than add a hoop to jump through. Closes lujax-dev#80 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
LewieJ08
approved these changes
Jul 17, 2026
LewieJ08
left a comment
LewieJ08
left a comment
Collaborator
There was a problem hiding this comment.
This pull request example is great and same as the issue template pr works perfectly with our workflow. thank you for contributing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds
.github/PULL_REQUEST_TEMPLATE.mdwith the sections listed in #80: description, related issue, type of change, how it was tested, and a short checklist (npm test, lint, docs).Kept it deliberately short per the issue — a handful of prompts to keep PRs consistent, not a hoop to jump through.
Related issue
Closes #80
How it was tested
Markdown renders correctly on the branch; no code changes.
🤖 Generated with Claude Code