Updated pr template with checklist

[dhirajudhani]

What kind of change does this PR introduce?
Documentation update - Enhanced PR template with test coverage and code quality checklists

Issue Number:

Fixes #2448

Did you add tests for your changes?
No

Snapshots/Videos:
No

If relevant, did you update the documentation?
Yes - This PR is a documentation update

Summary
Updated the PR template to include:

Checklist for implementing coderaabbitai suggestions
Checklist for verifying test coverage requirements (~90/95%)

Does this PR introduce a breaking change?
No

Other information

Have you read the contributing guide?

Summary by CodeRabbit

• New Features
  • Introduced a "Checklist" section in the pull request template to enhance code quality assurance.
  • Added checklist items for reviewing AI suggestions, writing tests, and confirming test coverage standards.
• Chores
  • Removed the previous question regarding the addition of tests in the pull request template.

[github-actions]

Our Pull Request Approval Process

We have these basic policies to make the approval process smoother for our volunteer team.

Testing Your Code

Please make sure your code passes all tests. Our test code coverage system will fail if these conditions occur:

1. The overall code coverage drops below the target threshold of the repository
2. Any file in the pull request has code coverage levels below the repository threshold
3. Merge conflicts

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.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

1. comments in this PR or
2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

1. arbitrators of future discussions with other contributors about the validity of your changes
2. point of contact for evaluating the validity of your work
3. person who verifies matching issues by others that should be closed.
4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

1. PRs with issues not assigned to you will be closed by the reviewer
2. Fix the first comment in the PR so that each issue listed automatically closes

Other

1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
2. Read the CONTRIBUTING.md file make

[coderabbitai]

Walkthrough

The pull request modifies the pull request template in .github/pull_request_template.md by introducing a new "Checklist" section. This section includes two categories: "CodeRabbit AI Review" and "Test Coverage," each containing specific checklist items to ensure adherence to CodeRabbit AI suggestions and verification of test coverage. Additionally, a question about adding tests has been removed for consistency.

Changes

File Path	Change Summary
.github/pull_request_template.md	Added "Checklist" section with items for CodeRabbit AI Review and Test Coverage; removed question about adding tests; minor formatting adjustments.

Assessment against linked issues

Objective	Addressed	Explanation
Update PR template to include a checklist for coderaabbitai suggestions (2448)	✅
Update PR template to verify that tests are written and coverage meets standards (2448)	✅
PR template is updated in the .github directory (2448)	✅

Poem

🐇 In the garden of code, we hop with delight,
A checklist now shines, making standards so bright.
With tests and suggestions, we flourish and grow,
Ensuring our quality continues to flow!
So let’s raise our carrots and cheer with a grin,
For a template that helps us all strive to win! 🌟

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between ffe0c0d and b9a1e2c.

📒 Files selected for processing (1)

• .github/pull_request_template.md (2 hunks)

🧰 Additional context used

🪛 Markdownlint

.github/pull_request_template.md

57-57: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

🔇 Additional comments (2)

.github/pull_request_template.md (2)

44-50: LGTM! Well-structured checklist for CodeRabbit AI review.

The checklist items effectively enforce the implementation of CodeRabbit AI suggestions while allowing for justified exceptions.

---

51-54: Duplicate: Test coverage percentage mismatch

---

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?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)

.github/pull_request_template.md (1)

26-30: Enhance checklist clarity with additional context.

The checklist effectively addresses the objectives from issue #2448. Consider these minor enhancements for better clarity:

 **Code Quality Checklist:**

-[ ] I have implemented all relevant CodeRabbit AI suggestions
+[ ] I have implemented all relevant CodeRabbit AI suggestions from the PR comments
 [ ] I have written tests for the changes made in this PR
-[ ] The test coverage meets or exceeds the current coverage threshold (~90-95%)
+[ ] The test coverage meets or exceeds 90% threshold

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 3ea2919 and 6bf0d90.

📒 Files selected for processing (1)

• .github/pull_request_template.md (2 hunks)

🔇 Additional comments (1)

.github/pull_request_template.md (1)

59-59: LGTM! Format change improves consistency.

The comment format for Yes/No response aligns well with other placeholder comments in the template.

[varshith257]

Once check Talawa -api PR. Make sure it follows the same

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.26%. Comparing base (d16b95e) to head (b9a1e2c).
Report is 3 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #2454   +/-   ##
========================================
  Coverage    98.26%   98.26%           
========================================
  Files          297      297           
  Lines         8638     8638           
  Branches      2486     2486           
========================================
  Hits          8488     8488           
  Misses         139      139           
  Partials        11       11           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[coderabbitai]

Actionable comments posted: 2

🧹 Outside diff range and nitpick comments (1)

.github/pull_request_template.md (1)

12-12: Clean up formatting inconsistencies

A few minor formatting improvements needed:

1. Remove extra newline after line 12
2. Reduce multiple consecutive newlines at line 56 to a single newline

Also applies to: 56-56

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 6bf0d90 and ffe0c0d.

📒 Files selected for processing (1)

• .github/pull_request_template.md (2 hunks)

🧰 Additional context used

🪛 Markdownlint

.github/pull_request_template.md

57-57: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

🔇 Additional comments (1)

.github/pull_request_template.md (1)

46-49: LGTM! Well-structured CodeRabbit AI review checklist

The checklist effectively enforces the implementation of CodeRabbit AI suggestions while allowing for justified exceptions.

[dhirajudhani]

@varshith257 hi have made required changes and it same as it is talawa-api once you review and approve i will create new pr for develop-postgress

Done

[varshith257]

@coderabbitai resolve

[coderabbitai]

✅ Actions performed

Comments resolved and changes approved.