Skip to main content
This section provides how-to guides showing you how to use Kosli to report changes from different CI systems.
Note that all CLI command flags can be set as environment variables by adding the the KOSLI_ prefix and capitalizing them.

Defaulted Kosli command flags from CI variables

The following flags are defaulted (which means you don’t need to provide the flags, they’ll be automatically set to values listed below) as follows in the CI systems below:
View defaulted Kosli command flags in Github Actions.
FlagDefault
—build-url<GITHUB_SERVER_URL>/<GITHUB_REPOSITORY>/actions/runs/<GITHUB_RUN_ID>
—commit-url<GITHUB_SERVER_URL>/<GITHUB_REPOSITORY>/commit/<GITHUB_SHA>
—commit<GITHUB_SHA>
—git-commit<GITHUB_SHA>
—repository<GITHUB_REPOSITORY>
—github-org<GITHUB_REPOSITORY_OWNER>
Where <PLACEHOLDERS> are Github Actions predefined variables. See here for more details.

Use Kosli in Github Actions

To use Kosli in Github Actions workflows, you can use the kosli CLI setup action to install the CLI on your Github Actions Runner. Then, you can use all the CLI commands in your workflows.

GitHub Secrets

Keep in mind that secrets in Github actions are not automatically exported as environment variables. You need to add required secrets to your GITHUB environment explicitly. E.g. to make kosli_api_token secret available for all cli commands as an environment variable use following:
env:
  KOSLI_API_TOKEN: ${{ secrets.kosli_api_token }}

Example

Here is an example Github Actions workflow snippet using kosli-dev/setup-cli-action running kosli create flow command:
jobs:
  example:
    runs-on: ubuntu-latest
    env:
      KOSLI_API_TOKEN: ${{ secrets.MY_KOSLI_API_TOKEN }}
      KOSLI_ORG: my-org
    steps:
      - name: setup kosli
        uses: kosli-dev/setup-cli-action@v2
      - name: create flow
        run: kosli create flow my-flow --template pull-request,artifact,test
For a complete example of a Github workflow using Kosli, please check the Kosli CLI’s own workflow.
Last modified on March 10, 2026