Skip to content

Revise pull request template with clearer sections and contributor checklist#27

Merged
SharkyBytes merged 1 commit intoAOSSIE-Org:mainfrom
ashi2004:patch-1
Mar 17, 2026
Merged

Revise pull request template with clearer sections and contributor checklist#27
SharkyBytes merged 1 commit intoAOSSIE-Org:mainfrom
ashi2004:patch-1

Conversation

@ashi2004
Copy link
Contributor

@ashi2004 ashi2004 commented Mar 16, 2026

Updated the pull request template to include new sections for collaboration, screenshots, and an AI notice.

Screenshots/Recordings:

Not applicable. This PR updates the pull request template structure and does not introduce any UI or functional changes.

Additional Notes:

I updated the Pull Request template to improve the contribution workflow and make it easier for contributors to provide structured information when opening a PR.

Changes include:
-> Added clearer sections for description, changes made, and screenshots/recordings
-> Added a collaboration section to acknowledge contributors working together
-> Included an AI usage notice to encourage responsible use of AI tools when contributing
-> Improved the contributor checklist for better PR quality

Additionally, the reference to CONTRIBUTING.md was removed/adjusted as it was causing issues due to the link not resolving correctly in the template.

These updates aim to make PR submissions more consistent and easier for maintainers to review.

Checklist

  • My code follows the project's code style and conventions
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings or errors
  • I have joined the Discord server and I will share a link to this PR with the project maintainers there
  • I have read the Contributing Guidelines

⚠️ AI Notice - Important!

We encourage contributors to use AI tools responsibly when creating Pull Requests. While AI can be a valuable aid, it is essential to ensure that your contributions meet the task requirements, build successfully, include relevant tests, and pass all linters. Submissions that do not meet these standards may be closed without warning to maintain the quality and integrity of the project. Please take the time to understand the changes you are proposing and their impact.

Summary by CodeRabbit

  • Chores
    • Enhanced pull request template with improved organization, updated section headings, and new collaboration placeholders for a streamlined contribution process.

@coderabbitai
Copy link

coderabbitai bot commented Mar 16, 2026

Walkthrough

The pull request template is restructured to reorganize sections and update naming conventions. "Addressed Issues" and "Screenshots/Recordings" are renamed to "Description", "Changes Made", and "Screenshots or Visual Changes". A "Collaboration" section is added, and two-column checklist items are removed with updated placeholder text.

Changes

Cohort / File(s) Summary
PR Template Restructure
.github/PULL_REQUEST_TEMPLATE.md
Reorganized template sections with renamed headings ("Description", "Changes Made", "Screenshots or Visual Changes") and added "Collaboration" section. Removed two-column checklist formatting and updated placeholder content.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested labels

Documentation

Poem

🐰 Hop, hop! The template's been rearranged,
With sections freshly renamed and exchanged,
Descriptions now flow, changes made shine bright,
Collaboration checklist—everything's just right!
A template reborn, neat and refined,
For pull requests perfectly aligned!

🚥 Pre-merge checks | ✅ 2
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main change: revising the PR template with clearer sections and an improved contributor checklist, which directly matches the file-level changes in .github/PULL_REQUEST_TEMPLATE.md.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
📝 Coding Plan
  • Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions github-actions bot added size/S and removed size/S labels Mar 16, 2026
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/PULL_REQUEST_TEMPLATE.md:
- Around line 24-27: The "Collaborated with: `@username` (optional)" line in the
PR template uses backticks which render the mention as inline code; remove the
surrounding backticks so the entry reads "Collaborated with: `@username`
(optional)" to enable proper GitHub mentions and linking. Update the template
text where the exact string "Collaborated with: `@username` (optional)" appears
to remove the backticks and keep the rest of the line unchanged.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: cc6b1cd8-dfae-4dbf-8885-043aca2ed1e8

📥 Commits

Reviewing files that changed from the base of the PR and between a3ccb2b and 0b4fcae.

📒 Files selected for processing (1)
  • .github/PULL_REQUEST_TEMPLATE.md

Comment on lines +24 to +27
## 🤝 Collaboration

<!-- If you collaborated with someone on this pull request, mention their GitHub username or name here. -->
Collaborated with: `@username` (optional)
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Fix the collaboration mention format.

The backticks around @username will render it as inline code rather than creating a proper GitHub mention. This prevents the collaborator from being notified and linked.

💬 Proposed fix to enable proper GitHub mentions
-Collaborated with: `@username` (optional)
+Collaborated with: `@username` (optional)

Without backticks, @username will create an actual mention that tags the user and creates a clickable link to their profile.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
## 🤝 Collaboration
<!-- If you collaborated with someone on this pull request, mention their GitHub username or name here. -->
Collaborated with: `@username` (optional)
## 🤝 Collaboration
<!-- If you collaborated with someone on this pull request, mention their GitHub username or name here. -->
Collaborated with: `@username` (optional)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.github/PULL_REQUEST_TEMPLATE.md around lines 24 - 27, The "Collaborated
with: `@username` (optional)" line in the PR template uses backticks which
render the mention as inline code; remove the surrounding backticks so the entry
reads "Collaborated with: `@username` (optional)" to enable proper GitHub mentions
and linking. Update the template text where the exact string "Collaborated with:
`@username` (optional)" appears to remove the backticks and keep the rest of the
line unchanged.

@SharkyBytes
Copy link
Contributor

LGTM

@SharkyBytes SharkyBytes merged commit 42d1d3c into AOSSIE-Org:main Mar 17, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants