From f7344fd7872e87d87810650fdf5f9dd2b9f34f58 Mon Sep 17 00:00:00 2001 From: mrT23 Date: Sun, 8 Sep 2024 17:31:17 +0300 Subject: [PATCH] metadata.md docs --- docs/docs/core-abilities/metadata.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/docs/core-abilities/metadata.md b/docs/docs/core-abilities/metadata.md index bcb91fae..d36c93e4 100644 --- a/docs/docs/core-abilities/metadata.md +++ b/docs/docs/core-abilities/metadata.md @@ -8,7 +8,8 @@ PR-Agent initially retrieves for each PR the following data: - PR diff patches, in [hunk diff](https://loicpefferkorn.net/2014/02/diff-files-what-are-hunks-and-how-to-extract-them/) format - The entire content of the files that were modified in the PR -In addition, PR-Agent can incorporate supplementary information provided by the user and more tailored to his specific preferences, like [`extra_instructions` and `organization best practices`](https://pr-agent-docs.codium.ai/tools/improve/#extra-instructions-and-best-practices) that can be used to enhance the PR analysis. +!!! tip "Tip: Organization-level metadata" + In addition to the inputs above, PR-Agent can incorporate supplementary preferences provided by the user, like [`extra_instructions` and `organization best practices`](https://pr-agent-docs.codium.ai/tools/improve/#extra-instructions-and-best-practices). This information can be used to enhance the PR analysis. (2) By default, the first command that PR-Agent executes is [`describe`](https://pr-agent-docs.codium.ai/tools/describe/), which generates three types of outputs: