Skip to content

Conversation

@rjpower
Copy link
Collaborator

@rjpower rjpower commented Jan 21, 2026

This updates our PR template to reflect that we now auto-test all code and prefer to have concise descriptions.

We automatically run pre-commit lints and tests, so the checklist feels superfluous.
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR updates the pull request template to better align with current practices, specifically reflecting that code is now auto-tested and encouraging more concise descriptions suitable for commit messages.

Changes:

  • Removed the checklist section (linting, testing, deletion reminder) since these steps are now automated
  • Added guidance requesting concise, paragraph-length descriptions with optional bullet points
  • Included a concrete example showing the preferred format and style for PR descriptions

[Please include a summary of the changes and the related issue.]
e.g.

Title: [RL] Fix loss: use global token normalization instead of per-example (#2376)
Copy link

Copilot AI Jan 21, 2026

Choose a reason for hiding this comment

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

The example title includes a specific PR number (#2376) which will become outdated and confusing as a template example. Consider using a generic placeholder like "(#XXXX)" or removing the PR number entirely from the example.

Suggested change
Title: [RL] Fix loss: use global token normalization instead of per-example (#2376)
Title: [RL] Fix loss: use global token normalization instead of per-example (#XXXX)

Copilot uses AI. Check for mistakes.
@rjpower
Copy link
Collaborator Author

rjpower commented Jan 22, 2026

@claude adjust this template to provide a place for an appropriate #fixes notation.

Add a note which the user should delete indicating that the PR should reference an existing issue for ongoing work.

@claude
Copy link

claude bot commented Jan 22, 2026

Claude finished @rjpower's task in 51s —— View job


Task: Update PR Template for Issue References

Successfully updated the PR template to include issue reference notation.

Todo List

  • Read current PR template file
  • Add appropriate #fixes notation area
  • Add deletable note about referencing existing issues
  • Commit and push changes

Changes Made

Added to the top of the PR template:

  • A Fixes # placeholder for issue references (which GitHub will use to auto-close issues when the PR is merged)
  • HTML comments with instructions that users should delete, reminding them that PRs for ongoing work should reference an existing issue

The template now starts with:

Fixes #

This addresses the feedback from Helw150's review comment and provides clear guidance for users while maintaining the concise format you wanted.

--- |

github-actions bot and others added 3 commits January 22, 2026 16:42
- Added 'Fixes #' placeholder for issue references (enables auto-close)
- Added deletable comment reminding users to reference existing issues
- Addresses feedback from review comments

Co-authored-by: Russell Power <rjpower@users.noreply.github.com>
Updated the pull request template to improve clarity and structure.
@rjpower rjpower disabled auto-merge January 22, 2026 16:46
@rjpower rjpower enabled auto-merge (squash) January 22, 2026 16:47
@rjpower rjpower requested a review from Helw150 January 22, 2026 16:50
Copy link
Member

@dlwh dlwh left a comment

Choose a reason for hiding this comment

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

maybe have agents.md link to this? people are using agents to write their pr descriptions now

@rjpower rjpower merged commit e6f52ca into main Jan 22, 2026
10 checks passed
@rjpower rjpower deleted the rjpower/20260120-cleanup-pr-template branch January 22, 2026 18:26
@rjpower
Copy link
Collaborator Author

rjpower commented Jan 22, 2026

sorry was on auto-merge, can add agents update separately

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.

4 participants