Skip to content

Update pr template #1605

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
JoannaaKL wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update pr template #1605

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3a75e3a
Update pr template
JoannaaKL Dec 15, 2025
75444e0
Add prompts tested section to PR template (#1617)
Copilot Dec 16, 2025
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
43 changes: 35 additions & 8 deletions .github/pull_request_template.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,11 +1,38 @@
<!--
Thank you for contributing to GitHub MCP Server!
Please reference an existing issue: `Closes #NUMBER`
Screenshots or videos of changed behavior is incredibly helpful and always appreciated.
Consider addressing the following:
- Tradeoffs: List tradeoffs you made to take on or pay down tech debt.
- Alternatives: Describe alternative approaches you considered and why you discarded them.
Copilot: Fill all sections. Prefer short, concrete answers.
If a checkbox is selected, add a brief explanation.
-->

Closes:
## Summary
<!-- In 1–2 sentences: what does this PR do? -->

## Why
Copy link
Collaborator

@SamMorrowDrums SamMorrowDrums Dec 15, 2025

Choose a reason for hiding this comment

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

Can we add a section asking to add prompts tested for triggering the tool (tool changes only)

I think we really want to understand what they want to achieve, not just their solution so that if we disagree with the solution we can still consider the problem they are hoping to solve and consider how we would solve it.

Collecting use-case would be high value for product.

Copy link
Contributor Author

@JoannaaKL JoannaaKL Dec 16, 2025

Choose a reason for hiding this comment

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

Good, point! @copilot add a section asking to add prompts tested for triggering the tool (only for tool changes).

<!-- Why is this change needed? Link issues or discussions. -->
Fixes #

## What changed
<!-- Bullet list of concrete changes. -->
-
-

## MCP impact
<!-- Select one or more. If selected, add 1–2 sentences. -->
- [ ] No tool or API changes
- [ ] Tool schema or behavior changed
- [ ] New tool added

## Security / limits
<!-- Select if relevant. Add a short note if checked. -->
- [ ] No security or limits impact
- [ ] Auth / permissions considered
- [ ] Data exposure, filtering, or token/size limits considered

## Lint & tests
<!-- Check what you ran. If not run, explain briefly. -->
- [ ] Linted locally with `./script/lint`
- [ ] Tested locally with `./script/test`

## Docs

- [ ] Not needed
- [ ] Updated (README / docs / examples)
Loading