diff --git a/docs/docs/tools/help_docs.md b/docs/docs/tools/help_docs.md index 308edc1d..19ba4180 100644 --- a/docs/docs/tools/help_docs.md +++ b/docs/docs/tools/help_docs.md @@ -86,10 +86,11 @@ jobs: -c "cd /app && \ echo 'Running Issue Agent action step on ISSUE_URL=$ISSUE_URL' && \ export config__git_provider='github' && \ - export github__user_token=$GITHUB_TOKEN && \ + export github__user_token=$GITHUB_TOKEN && \ export github__base_url=$GITHUB_API_URL && \ export openai__key=$OPENAI_KEY && \ - python -m pr_agent.cli --issue_url=$ISSUE_URL --pr_help_docs.repo_url="..." --pr_help_docs.docs_path="..." --pr_help_docs.openai_key=$OPENAI_KEY && \help_docs \"$ISSUE_BODY\"" + python -m pr_agent.cli --issue_url=$ISSUE_URL --pr_help_docs.repo_url="..." --pr_help_docs.docs_path="..." --pr_help_docs.openai_key=$OPENAI_KEY && \ + help_docs "$ISSUE_BODY" ``` 3) Following completion of the remaining steps (such as adding secrets and relevant configurations, such as `repo_url` and `docs_path`) merge this change to your main branch. diff --git a/docs/docs/tools/improve_component.md b/docs/docs/tools/improve_component.md index 6b93b621..05f1371e 100644 --- a/docs/docs/tools/improve_component.md +++ b/docs/docs/tools/improve_component.md @@ -1,6 +1,6 @@ ## Overview -The `improve_component` tool generates code suggestions for a specific code component that changed in the PR. +The `improve_component` tool generates code suggestions for a specific code component that has changed in the PR. it can be invoked manually by commenting on any PR: ``` diff --git a/docs/docs/tools/review.md b/docs/docs/tools/review.md index 9705f260..7665202a 100644 --- a/docs/docs/tools/review.md +++ b/docs/docs/tools/review.md @@ -1,6 +1,6 @@ ## Overview -The `review` tool scans the PR code changes, and generates a list of feedbacks about the PR, aiming to aid the reviewing process. +The `review` tool scans the PR code changes, and generates feedback about the PR, aiming to aid the reviewing process.
The tool can be triggered automatically every time a new PR is [opened](../usage-guide/automations_and_usage.md#github-app-automatic-tools-when-a-new-pr-is-opened), or can be invoked manually by commenting on any PR: @@ -8,7 +8,7 @@ The tool can be triggered automatically every time a new PR is [opened](../usage /review ``` -Note that the main purpose of the `review` tool is to provide the **PR reviewer** with useful feedbacks and insights. The PR author, in contrast, may prefer to save time and focus on the output of the [improve](./improve.md) tool, which provides actionable code suggestions. +Note that the main purpose of the `review` tool is to provide the **PR reviewer** with useful feedback and insights. The PR author, in contrast, may prefer to save time and focus on the output of the [improve](./improve.md) tool, which provides actionable code suggestions. (Read more about the different personas in the PR process and how Qodo Merge aims to assist them in our [blog](https://www.codium.ai/blog/understanding-the-challenges-and-pain-points-of-the-pull-request-cycle/)) diff --git a/docs/docs/tools/similar_code.md b/docs/docs/tools/similar_code.md index 684f8265..f65f875c 100644 --- a/docs/docs/tools/similar_code.md +++ b/docs/docs/tools/similar_code.md @@ -6,7 +6,7 @@ The similar code tool retrieves the most similar code components from inside the For example: -`Global Search` for a method called `chat_completion`: +A `Global Search` for a method called `chat_completion`: ![similar code global](https://codium.ai/images/pr_agent/similar_code_global2.png){width=768} @@ -21,7 +21,7 @@ Search result link example: ![code search result single](https://codium.ai/images/pr_agent/code_search_result_single.png){width=768} -`Organization Search`: +An `Organization Search`: ![similar code org](https://codium.ai/images/pr_agent/similar_code_org.png){width=768} diff --git a/docs/docs/tools/test.md b/docs/docs/tools/test.md index 04cc33d6..22f4df01 100644 --- a/docs/docs/tools/test.md +++ b/docs/docs/tools/test.md @@ -1,6 +1,6 @@ ## Overview -By combining LLM abilities with static code analysis, the `test` tool generate tests for a selected component, based on the PR code changes. +By combining LLM abilities with static code analysis, the `test` tool generates tests for a selected component, based on the PR code changes. It can be invoked manually by commenting on any PR: ```