Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 27 additions & 6 deletions .github/pull_request_template.md
Original file line number Diff line number Diff line change
@@ -1,15 +1,36 @@
## Summary of Changes
## Summary of Changes


## Related GitHub Issue(s)

## Related GitHub Issue(s)
<!-- Use keywords like close/closes/closed or fix/fixes/fixed to close the issue automatically -->

## Additional Context for Reviewers

## AI/LLM Usage
<!-- Declare and briefly describe any AI/LLM assistance used and the extent of usage during development of this PR. -->



<!-- Do not edit anything below this. -->
## Additional Context for Reviewers



<!-- Do not edit anything below until the ticket is open. Checklists below. -->

## Submitter's Checklist
- [ ] I have reviewed and am adhering to the standards outlined in the project [Governing Doc](https://github.com/casact/chainladder-python/blob/main/docs/library/governance.md).
- [ ] The PR subject title summarizes the changes, with one proper prefix (`[FIX]`, `[FEAT]`, `[DOCS]`, `[TST]`, `[CHORE]`, or `[BRK]`).
- [ ] I am a human (not a bot), and this PR form is written by a human.

## Reviewer's Checklist
- [ ] The implementation addresses the associated issue(s).
- [ ] The implementation is appropriate, maintainable, and follows ARCHITECTURE.md.
- [ ] PR subject title has the proper prefix and the subject is appropriate.
- [ ] Relevant issue(s) are linked.
- [ ] AI/LLM usage is disclosed and appropriate.
- [ ] Documentation and tests are appropriate.
- [ ] Additional reviewer is requested or not needed.
- [ ] CI tests passed or failure are acceptable.



## Checklist
- [ ] I passed tests locally for both code (`uv run pytest`) and documentation changes (`uv run --directory docs jb build . --builder=custom --custom-builder=doctest`)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd recommend adding a bullet Submitter's Checklist that replaces this one. We now have a pre-commit hook that can one-shot all the workflows locally:

I passed all pre-commit checks prior to push (with a link to the list of workflows we deploy in the Governing Doc).

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you think this is necessary? We already have the CI tests that run automatically, and there's also the last bullet on the reviewer's list "CI tests passed or failure are acceptable"

Loading