Improve PR template with testing and security checklist#45
Improve PR template with testing and security checklist#45ArmanKumar456 wants to merge 1 commit into
Conversation
|
@ArmanKumar456 is attempting to deploy a commit to the Harsh Yadav's projects Team on Vercel. A member of the Team first needs to authorize it. |
📝 WalkthroughWalkthroughThe pull request template is updated to a security-first Gsecure-specific format. The template adds a prominent security header, restructures sections with expanded testing details including environment and coverage, introduces a dedicated security checklist, and replaces the previous compact checklist with more granular hygiene and code quality checks. ChangesPR Template Security-First Restructuring
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment Warning |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
🎉 Thank you @ArmanKumar456 for your first PR to Gsecure!
We really appreciate your contribution 🙌
What happens next:
- 🔍 Maintainers will review your PR
- 🧪 Automated checks will run
- ✨ Feedback may be shared if needed
Please confirm your PR includes:
- ✔️ Clear summary of changes
- ✔️ Linked issue (e.g., Fixes #123)
- ✔️ Steps to test
- ✔️ Screenshots (for UI changes)
📘 Contribution Standards:
👉 https://github.com/HarshYadav152/Gsecure/blob/main/CONTRIBUTING.md
💬 Stay Connected with Our Community
💚 WhatsApp (Friendly Community)
For informal chats, quick help, and building friendships with contributors:
👉 https://chat.whatsapp.com/I8GYXd3mHlDCC2iXhNGeqV
🌟 Our Philosophy: We value both professional collaboration (Discord) and personal connections (WhatsApp). Join both to get the complete SS-Capture community experience!
Thanks for helping improve Gsecure 🚀
Let's build something amazing together! 💪
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/PULL_REQUEST_TEMPLATE.md:
- Around line 46-52: The Test Environment section's markdown heading "### Test
Environment" is immediately adjacent to the table, triggering MD058; insert a
single blank line between the heading and the table and another blank line after
the table so the table is separated from surrounding content (i.e., add an empty
line before the line starting with "| | |" and one after the final table row) to
satisfy blanks-around-tables.
🪄 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: defaults
Review profile: CHILL
Plan: Pro
Run ID: ba897108-9e28-4279-b1b1-0208dfc88f03
📒 Files selected for processing (1)
.github/PULL_REQUEST_TEMPLATE.md
| ### Test Environment | ||
| | | | | ||
| |---|---| | ||
| | **OS** | | | ||
| | **Browser & Version** | | | ||
| | **Node.js Version** | | | ||
|
|
There was a problem hiding this comment.
Add blank lines around the Test Environment table.
Line 47 violates markdownlint MD058 (blanks-around-tables). Add an empty line between the heading and table (and keep one after the table) to avoid lint failures.
Suggested fix
### Test Environment
+
| | |
|---|---|
| **OS** | |
| **Browser & Version** | |
| **Node.js Version** | |
+📝 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.
| ### Test Environment | |
| | | | | |
| |---|---| | |
| | **OS** | | | |
| | **Browser & Version** | | | |
| | **Node.js Version** | | | |
| ### Test Environment | |
| | | | | |
| |---|---| | |
| | **OS** | | | |
| | **Browser & Version** | | | |
| | **Node.js Version** | | | |
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 47-47: Tables should be surrounded by blank lines
(MD058, blanks-around-tables)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In @.github/PULL_REQUEST_TEMPLATE.md around lines 46 - 52, The Test Environment
section's markdown heading "### Test Environment" is immediately adjacent to the
table, triggering MD058; insert a single blank line between the heading and the
table and another blank line after the table so the table is separated from
surrounding content (i.e., add an empty line before the line starting with "| |
|" and one after the final table row) to satisfy blanks-around-tables.
Source: Linters/SAST tools
1 participant
Summary
Updated the pull request template to provide better structure for contributors and reviewers.
Changes Made
Testing
Related Issue
Fixes #41
Checklist
Summary by CodeRabbit