Merge branch 'main' into azure

jmacdotorg · web-flow · commit 7b6fd28ca4a0 · 2025-07-18T10:46:36.000-04:00
diff --git a/docs/changelog.md b/docs/changelog.md
@@ -5,6 +5,28 @@ description: The latest updates and changes to CodeRabbit.
 sidebar_position: 13
 ---
 
+## July 17, 2025
+
+### Enhanced Reporting Capabilities
+
+We're excited to announce significant improvements to our reporting system that will make your automated reports more powerful and actionable!
+
+#### Exclusion Filters with NOT_IN Option
+
+Reports now support exclusion filters using the `NOT_IN` option, allowing you to filter out pull requests based on their repository, label, user, or team. This gives you more granular control over what appears in your reports, helping you focus on the most relevant information.
+
+#### Next Steps Section in Daily Standup Reports
+
+We've enhanced the default daily standup report template to include a "Next Steps" section. This provides clear guidance on what actions authors and reviewers should take regarding each pull request or change, making your reports more actionable and helping teams stay on track.
+
+#### CI/CD GitHub Action Check Status Awareness
+
+Reports now include CI/CD GitHub Action check status as a data source. Your reports will be aware of which CI/CD checks are failing or passing, giving you better visibility into the health of your pull requests and helping identify potential issues before they become blockers.
+
+#### Score Card Custom Report Option
+
+We've added a new optional score card report feature that allows you to grade and create report cards for your developers. This custom report optional data source provides a structured way to evaluate developer performance and contributions. See our [custom reports documentation](/guides/custom-reports#remove-prs-without-a-score-cardchart-bot-comment) for more details on how to implement score cards in your reports.
+
 ## July 10, 2025
 
 ### Enhanced Python Static Analysis: nbqa Support for Jupyter Notebooks
diff --git a/docs/guides/custom-reports.md b/docs/guides/custom-reports.md
@@ -117,6 +117,14 @@ Contained within the `<pr_details>` tag.
   - `<comment_updated_at>`: datetime - The date and time the comment was last updated.
   - `<comment_body>`: markdown - The content of the comment.
 
+#### CI/CD Check Status
+
+- `<pr_checks>`: array of check objects - Contains all CI/CD checks for the PR. _GitHub Only_.
+- `<pr_check>`: object - Each individual check is wrapped in this tag and is an object with the following properties:
+  - `<pr_check_name>`: string - The name of the CI/CD check.
+  - `<pr_check_status>`: string - The status of the check (e.g., "success", "failure", "in_progress", "canceled").
+  - `<pr_check_url>`: string - The URL to view the detailed results of the check.
+
 Here's an example prompt that uses these data points:
 
 ```text
@@ -299,7 +307,7 @@ Issues and tickets brings in conversations, descriptions, and comments from Jira
 
 This option gives you the ability to create a report limited only to pull requests containing a "Score Card" or "Score Chart" bot comment from CodeRabbit or other bots. To enable issues and tickets you must include the tag `<pr_score_card>` in your prompt.
 
-> **IMPORTANT:** This will automatically remove any pull requests from your reports if they do not contain a "Score Card" or "Score Chart" bot comment. Using this option without setting up a flow to create these comments will result in `No new pull request activity in the last XYZ hours` errors. Do not enable this option unless you have created a "Score Card" or "Score Chart" bot comment flow.
+> **IMPORTANT:** This will automatically remove any pull requests from your reports if they do not contain a "Score Card" or "Score Chart" bot comment. Using this option without setting up a flow to create these comments will result in `No new pull request activity in the last XYZ hours` errors. Do not enable this option unless you have asked coderabbit to create a "Score Card" thourhg a comment or implimented the "Score Chart" bot comment flow below.
 
 For example you can ask coderabbit to check serveral conditions on a pull request and produce a "Score Chart":
 
@@ -340,7 +348,7 @@ Generate a weekly code review report for the author of this pull request only fo
    - `1` → Passed
 
 **Final Score Calculation:**
-Combine the scores from the parameters above to derive the final code quality score (out of 5).
+Combine the scores from the parameters above to derive the final code quality score (out of 9).
 **Output Format:**
 Provide the final report in a table format with the following columns (use shorthand notations), be sure to include this list at the top above the chart in the "Column Notation" section so users understand what the columns mean:
 
diff --git a/docs/guides/scheduled-reports.md b/docs/guides/scheduled-reports.md
@@ -52,11 +52,12 @@ Choose a time that works for all team members, especially for distributed teams
 
 ### Report Parameters
 
-Reports can be filtered using multiple parameters:
+Reports can be filtered using multiple parameters, match pull requests using the **IN** option and exclude pull requests using the **NOT_IN** option:
 
 - **Repositories**: Select specific repositories to monitor
 - **Labels**: Filter by GitHub labels with operators:
   - IN: Match any selected label
+  - NOT_IN: Exclude any pr with select label
   - ALL: Match all selected labels
 - **Users**: Filter by specific GitHub users
 - **Teams**: Filter by organization teams
diff --git a/static/schema/schema.v2.json b/static/schema/schema.v2.json
@@ -374,6 +374,81 @@
 							"additionalProperties": false,
 							"default": {}
 						},
+						"pre_merge_checks": {
+							"type": "object",
+							"properties": {
+								"docstrings": {
+									"type": "object",
+									"properties": {
+										"mode": {
+											"type": "string",
+											"enum": ["off", "warning", "error"],
+											"default": "warning",
+											"description": "Mode | Level of enforcement for docstring coverage check. Warning only generates a warning and does not require the user to resolve the check. While error requires the user to resolve issues before merging pull request."
+										},
+										"threshold": {
+											"type": "number",
+											"minimum": 0,
+											"maximum": 100,
+											"default": 80,
+											"description": "Percentage threshold for docstring coverage check."
+										}
+									},
+									"additionalProperties": false,
+									"default": {},
+									"description": "Docstring Coverage | Checks if the code has sufficient docstrings."
+								},
+								"title": {
+									"type": "object",
+									"properties": {
+										"mode": {
+											"type": "string",
+											"enum": ["off", "warning", "error"],
+											"default": "warning",
+											"description": "Mode | Level of enforcement for pull request title check. Warning only generates a warning and does not require the user to resolve the check. While error requires the user to resolve issues before merging pull request."
+										},
+										"requirements": {
+											"type": "string",
+											"default": "",
+											"description": "Requirements | Requirements for the pull request title. Example: 'Title should be concise and descriptive, ideally under 50 characters.'"
+										}
+									},
+									"additionalProperties": false,
+									"default": {},
+									"description": "Title Check | Checks if the pull request title is appropriate and follows best practices."
+								},
+								"description": {
+									"type": "object",
+									"properties": {
+										"mode": {
+											"type": "string",
+											"enum": ["off", "warning", "error"],
+											"default": "warning",
+											"description": "Mode | Level of enforcement for pull request description check. Warning only generates a warning and does not require the user to resolve the check. While error requires the user to resolve issues before merging pull request."
+										}
+									},
+									"additionalProperties": false,
+									"default": {},
+									"description": "Description Check | Checks if the pull request description is appropriate and follows best practices."
+								},
+								"issue_assessment": {
+									"type": "object",
+									"properties": {
+										"mode": {
+											"type": "string",
+											"enum": ["off", "warning", "error"],
+											"default": "warning",
+											"description": "Mode | Level of enforcement for linked issue assessment. Warning only generates a warning and does not require the user to resolve the check. While error requires the user to resolve issues before merging pull request."
+										}
+									},
+									"additionalProperties": false,
+									"default": {},
+									"description": "Linked Issue Assessment | Checks if the pull request addresses the linked issues. Generate an assessment of how well the changes address the linked issues."
+								}
+							},
+							"additionalProperties": false,
+							"default": {}
+						},
 						"tools": {
 							"type": "object",
 							"properties": {
@@ -988,11 +1063,6 @@
 							"additionalProperties": false,
 							"description": "Tools that provide additional context to code reviews.",
 							"default": {}
-						},
-						"pre_merge_checks": {
-							"type": "object",
-							"additionalProperties": {},
-							"default": {}
 						}
 					},
 					"additionalProperties": false,
