-
-
Notifications
You must be signed in to change notification settings - Fork 1k
Feature/change PR template with check list added. #2694
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.
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
Feature/change PR template with check list added. #2694
Conversation
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
WalkthroughThe changes in this pull request involve modifications to the pull request template located in Changes
Assessment against linked issues
Poem
📜 Recent review detailsConfiguration used: .coderabbit.yaml 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
Our Pull Request Approval ProcessWe have these basic policies to make the approval process smoother for our volunteer team. Testing Your CodePlease make sure your code passes all tests. Our test code coverage system will fail if these conditions occur:
The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing. ReviewersDo not assign reviewers. Our Queue Monitors will review your PR and assign them.
Reviewing Your CodeYour reviewer(s) will have the following roles:
CONTRIBUTING.mdRead our CONTRIBUTING.md file. Most importantly:
Other
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 2
🧹 Outside diff range and nitpick comments (1)
.github/pull_request_template.md (1)
44-54
: Consider moving the checklist section for better visibilityThe checklist is currently placed at the end of the template. Consider moving it to the top, right after the branching strategy notice, to ensure contributors see and complete it first.
This would help enforce the standards earlier in the PR process.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
📒 Files selected for processing (1)
.github/pull_request_template.md
(1 hunks)
🔇 Additional comments (1)
.github/pull_request_template.md (1)
44-45
: LGTM!
The checklist header is clear and well-formatted.
@HarshDodiya1 implement coderaabbitai suggestions of coderaabbitai checklist |
Okay @varshith257, I have added the suggested checklist. |
✅ Actions performedReview triggered.
|
@coderabbitai resolve |
✅ Actions performedComments resolved and changes approved. |
e978dd7
into
PalisadoesFoundation:develop
Hey @varshith257, I am very much thankful to you. I have merged my first PR to a large org. I will always remember this. 🙂 Can I do the same for the |
Yes, go ahead |
What kind of change does this PR introduce?
feature change
Issue Number:
Fixes #2689
Did you add tests for your changes?
No
Snapshots/Videos:

If relevant, did you update the documentation?
No
Summary
The
pull_request_template.md
file now contains new added check list forDoes this PR introduce a breaking change?
No
Other information
Have you read the contributing guide?
Yes
Summary by CodeRabbit
New Features
Documentation