📋 Configuration and Parameters

📌 Introduction

This section contains complete reference information on all tool configuration parameters. Below is a list of available parameters for configuring the tool using CI/CD environment variables.

1. Description of environment variables

To configure the tool, you can use environment variables, which will be automatically recognized and used at startup.

CC_BASE_URL → Server address for the AI model. You usually need to ask the administrator what global environment variable they have set for your team and use that as the value for this variable. Each team has its own environment variable.
CC_API_KEY → API key for using the AI model. You usually need to ask the administrator what global environment variable they have set for your team and use that as the value for this variable. Each team has its own environment variable.
CC_MODEL → AI Model name. You usually need to ask the administrator what global environment variable they have set for your team and use that as the value for this variable. Each team has its own environment variable.
VCS_ACCESS_TOKEN → The reviewer's token with read and write permissions for PullRequests and repositories, as well as read permissions for user information. This is usually a common user for all teams. Ask the administrator about this value. As a rule, this is another global environment variable.
WORKSPACE → Workspace name. Usually located in the $BITBUCKET_WORKSPACE environment variable.
REPO_SLUG → Repository name. Usually located in the $BITBUCKET_REPO_SLUG environment variable.
SOURCE_BRANCH → Source branch name. Usually located in the $BITBUCKET_BRANCH environment variable.
PR_ID → Pull request ID. Usually located in the $BITBUCKET_PR_ID environment variable.
SOURCE_COMMIT → Commit hash of the source branch. Usually located in the $BITBUCKET_COMMIT environment variable.
PR_DESTINATION_BRANCH → Destination branch name. Usually located in the $BITBUCKET_PR_DESTINATION_BRANCH environment variable.
PR_DESTINATION_COMMIT → Commit hash of the destination branch. Usually located in the $BITBUCKET_PR_DESTINATION_COMMIT environment variable.
ATLASSIAN_USER_EMAIL → Reviewer's email address. This is usually a common user for all teams. Ask the administrator about this value. As a rule, this is another global environment variable.
TEAM_NAME → Reserved team name. It is important to set a value from a clearly defined list.
LOG_LEVEL → Logging level. Not usually used. Only if some kind of monitoring is required.
OPTIONS_TYPE → Value for determining the location of settings. Usually used to specify the location of settings for overriding the built-in review prompt.
CC_PROMPT → New prompt value. It is necessary to override the value of the prompt via arguments.
CC_ALLOWED_TOOL → List of permitted tools for AI. It is necessary to override the value of the allowed tools via arguments.
CC_DISALLOWED_TOOL → List of forbidden tools for AI. It is necessary to override the value of the forbidden tools via arguments.
ENABLE_REVIEWER_VERIFICATION → Value true or false. If not specified, the value true is used. Allows you to disable validation of Pull Request and reviewer presence. Useful when using an overridden value of the OPTIONS_TYPE variable.

📋 Configuration and Parameters

📌 Introduction

1. Description of environment variables

🤖 Kodo AI Reviewer

📚 Gitea

👩‍💻 Developer

🧑‍🔧 Tech Lead

📚 Bitbucket

👩‍💻 Developer

🧑‍🔧 Tech Lead

📚 Local Kodo