Danger

Danger automates code reviews through CI tools, aiding both code reviewers and developers who submit pull requests. It reduces the time reviewers spend on routine tasks, allowing more efficient code evaluation.

You can easily automate opened PRs with Appcircle's Danger integration.

For detailed information on the benefits that Danger, please refer to the following blog post:

Danger in CI: Automate Your Mobile Code Reviews - Appcircle Blog

Did you know that you can set rules for your code reviews and make sure they are checked before submitted? You can with running Danger in CI.

appcircle.io

danger

This tool does not support AzureDevOps. Therefore, if your repository is hosted on AzureDevOps, this tool will not function. Please use the Azure Bot for Swiftlint(for iOS) and Azure Bot for Detekt Report(for Android) components instead.

Prerequisites

The workflow steps that need to be executed before running the Danger step vary depending on the platform and are listed below:

Prerequisite Workflow Step	Description
Git Clone	The repository needs to be cloned to begin the badge-adding process. After this step, the variable AC_REPOSITORY_DIR will be set.

caution

Note that this component synchronizes with the Appcircle Triggers. Without a setup trigger, opening a PR will not trigger the pipeline, and Danger will not function.

Input Variables

Below is a list of input variables that can be used with this component with a description of each.

danger

Avoid hard-coding sensitive information like tokens and API keys directly into the step parameters.

We recommend using Environment Variables groups for such sensitive variables.

Variable Name	Description	Status
$AC_REPOSITORY_DIR	Specifies the cloned repository directory. This path will be generated after the Git Clone step.	Required
$AC_DANGER_PATH	Specifies path of Dangerfile. This path comes from AC_REPOSITORY_DIR. If DangerFile is in main directory of your repository. Do not change.	Required
$AC_DANGER_EXTRA_PARAMETERS	Extra command line parameters. For Example: enter --verbose for verbose mode.	Optional
$DANGER_GITHUB_API_TOKEN	Github Access Token for the bot user.	Optional
$DANGER_GITHUB_HOST	The host that GitHub is running on. For example: git.corp.com	Optional
$DANGER_GITHUB_API_BASE_URL	The host that the GitHub Enterprise API is reachable on. For example: https://git.corp.com/api/v3	Optional
$DANGER_GITLAB_API_TOKEN	GitLab Access Token for the bot user.	Optional
$DANGER_GITLAB_HOST	The host that GitLab is running on. For example: git.corp.com	Optional
$DANGER_GITLAB_API_BASE_URL	The host that the GitHub Enterprise API is reachable on. For example: https://git.corp.com/api/v4	Optional
$DANGER_BITBUCKETCLOUD_USERNAME	Bitbucket username for the bot user.	Optional
$DANGER_BITBUCKETCLOUD_PASSWORD	Bitbucket password for the bot user.	Optional
$DANGER_BITBUCKETCLOUD_UUID	Bitbucket UUID of the bot user.	Optional
$DANGER_BITBUCKETSERVER_USERNAME	Bitbucket username for the bot user.	Optional
$DANGER_BITBUCKETSERVER_PASSWORD	Bitbucket password for the bot user.	Optional
$DANGER_BITBUCKETSERVER_HOST	The host that Bitbucket is running on. For example: git.corp.com	Optional

To access the source code of this component, please use the following link:

GitHub - appcircleio/appcircle-danger-component

Contribute to appcircleio/appcircle-danger-component development by creating an account on GitHub.

github.com