Merge remote-tracking branch 'origin/main'

docs/docs/core-abilities/incremental_update.md

@@ -0,0 +1,33 @@
+# Incremental Update 💎
+
+`Supported Git Platforms: GitHub`
+
+## Overview
+The Incremental Update feature helps users focus on feedback for their newest changes, making large PRs more manageable.
+
+### How it works
+
+=== "Update Option on Subsequent Commits"
+    ![code_suggestions_update](https://www.qodo.ai/images/pr_agent/inc_update_before.png){width=512}
+
+=== "Generation of Incremental Update"
+    ![code_suggestions_inc_update_result](https://www.qodo.ai/images/pr_agent/inc_update_shown.png){width=512}
+
+___
+
+Whenever new commits are pushed following a recent code suggestions report for this PR, an Update button appears (as seen above).
+
+Once the user clicks on the button:
+
+- The `improve` tool identifies the new changes (the "delta")
+- Provides suggestions on these recent changes
+- Combines these suggestions with the overall PR feedback, prioritizing delta-related comments
+- Marks delta-related comments with a textual indication followed by an asterisk (*) with a link to this page, so they can easily be identified
+
+### Benefits for Developers
+
+- Focus on what matters: See feedback on newest code first
+- Clearer organization: Comments on recent changes are clearly marked
+- Better workflow: Address feedback more systematically, starting with recent changes
+
+

docs/docs/core-abilities/index.md

@@ -8,6 +8,7 @@ Qodo Merge utilizes a variety of core abilities to provide a comprehensive and e
 - [Dynamic context](https://qodo-merge-docs.qodo.ai/core-abilities/dynamic_context/)
 - [Fetching ticket context](https://qodo-merge-docs.qodo.ai/core-abilities/fetching_ticket_context/)
 - [Impact evaluation](https://qodo-merge-docs.qodo.ai/core-abilities/impact_evaluation/)
+- [Incremental Update](https://qodo-merge-docs.qodo.ai/core-abilities/incremental_update/)
 - [Interactivity](https://qodo-merge-docs.qodo.ai/core-abilities/interactivity/)
 - [Local and global metadata](https://qodo-merge-docs.qodo.ai/core-abilities/metadata/)
 - [RAG context enrichment](https://qodo-merge-docs.qodo.ai/core-abilities/rag_context_enrichment/)

docs/docs/index.md

@@ -67,6 +67,7 @@ PR-Agent and Qodo Merge offers extensive pull request functionalities across var
 |       | [Impact Evaluation](https://qodo-merge-docs.qodo.ai/core-abilities/impact_evaluation/) 💎               |   ✅   |   ✅   |           |              | 
 |       | [Code Validation 💎](https://qodo-merge-docs.qodo.ai/core-abilities/code_validation/)                   |   ✅   |   ✅   |    ✅     |      ✅      |
 |       | [Auto Best Practices 💎](https://qodo-merge-docs.qodo.ai/core-abilities/auto_best_practices/)                     |   ✅   |      |         |            |
+|       | [Incremental Update 💎](https://qodo-merge-docs.qodo.ai/core-abilities/incremental_update/)                   |   ✅   |      |         |            |
 !!! note "💎 means Qodo Merge only"
       All along the documentation, 💎 marks a feature available only in [Qodo Merge](https://www.codium.ai/pricing/){:target="_blank"}, and not in the open-source version.
 

docs/docs/installation/github.md

@@ -193,9 +193,8 @@ For example: `GITHUB.WEBHOOK_SECRET` --> `GITHUB__WEBHOOK_SECRET`
 3. Push image to ECR
 
     ```shell
-
- docker tag codiumai/pr-agent:serverless <AWS_ACCOUNT>.dkr.ecr.<AWS_REGION>.amazonaws.com/codiumai/pr-agent:serverless
- docker push <AWS_ACCOUNT>.dkr.ecr.<AWS_REGION>.amazonaws.com/codiumai/pr-agent:serverless
+    docker tag codiumai/pr-agent:serverless <AWS_ACCOUNT>.dkr.ecr.<AWS_REGION>.amazonaws.com/codiumai/pr-agent:serverless
+    docker push <AWS_ACCOUNT>.dkr.ecr.<AWS_REGION>.amazonaws.com/codiumai/pr-agent:serverless
     ```
 
 4. Create a lambda function that uses the uploaded image. Set the lambda timeout to be at least 3m.

docs/docs/tools/documentation.md

@@ -26,6 +26,29 @@ You can state a name of a specific component in the PR to get documentation only
 /add_docs component_name
 ```
 
+## Manual triggering
+
+Comment `/add_docs` on a PR to invoke it manually.
+
+## Automatic triggering
+
+To automatically run the `add_docs` tool when a pull request is opened, define in a [configuration file](https://qodo-merge-docs.qodo.ai/usage-guide/configuration_options/):
+
+
+```toml
+[github_app]
+pr_commands = [
+    "/add_docs",
+    ...
+]
+```
+
+The `pr_commands` list defines commands that run automatically when a PR is opened.
+Since this is under the [github_app] section, it only applies when using the Qodo Merge GitHub App in GitHub environments.
+
+!!! note
+By default, /add_docs is not triggered automatically. You must explicitly include it in pr_commands to enable this behavior.
+
 ## Configuration options
 
 - `docs_style`: The exact style of the documentation (for python docstring). you can choose between: `google`, `numpy`, `sphinx`, `restructuredtext`, `plain`. Default is `sphinx`.

docs/docs/tools/review.md

@@ -70,6 +70,10 @@ extra_instructions = "..."
         <td><b>enable_help_text</b></td>
         <td>If set to true, the tool will display a help text in the comment. Default is true.</td>
       </tr>
+      <tr>
+        <td><b>num_max_findings</b></td>
+        <td>Number of maximum returned findings. Default is 3.</td>
+      </tr>
     </table>
 
 !!! example "Enable\\disable specific sub-sections"
@@ -112,7 +116,7 @@ extra_instructions = "..."
       </tr>
       <tr>
         <td><b>enable_review_labels_effort</b></td>
-        <td>If set to true, the tool will publish a 'Review effort [1-5]: x' label. Default is true.</td>
+        <td>If set to true, the tool will publish a 'Review effort x/5' label (1–5 scale). Default is true.</td>
       </tr>
     </table>
 
@@ -141,7 +145,7 @@ extra_instructions = "..."
     The `review` tool can auto-generate two specific types of labels for a PR:
 
     - a `possible security issue` label that detects if a possible [security issue](https://github.com/Codium-ai/pr-agent/blob/tr/user_description/pr_agent/settings/pr_reviewer_prompts.toml#L136) exists in the PR code (`enable_review_labels_security` flag)
-    - a `Review effort [1-5]: x` label, where x is the estimated effort to review the PR (`enable_review_labels_effort` flag)
+    - a `Review effort x/5` label, where x is the estimated effort to review the PR on a 1–5 scale (`enable_review_labels_effort` flag)
 
     Both modes are useful, and we recommended to enable them.
 

docs/docs/usage-guide/additional_configurations.md

@@ -50,7 +50,7 @@ glob = ['*.py']
 And to ignore Python files in all PRs using `regex` pattern, set in a configuration file:
 
 ```
-[regex]
+[ignore]
 regex = ['.*\.py$']
 ```