> For the complete documentation index, see [llms.txt](https://docs.logilica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.logilica.com/integration/connecting-tools/github-actions.md).

# GitHub Actions

The GitHub Actions connector imports your workflow runs into Logilica so build performance and reliability feed into the [Build dashboard](/metrics-and-reports/build.md), and — once deployment detection is configured — the [DORA metrics](/configuration/dora-configuration.md).

## Authentication

GitHub Actions data is imported through your existing GitHub connection — there is no separate connector to configure. Once GitHub is connected (via OAuth, a personal access token, or a GitHub App installation), Logilica imports workflow run data for each repository automatically. See [Connecting Tools](/integration/connecting-tools.md) for how to set up the GitHub connection.

## What's Imported

For each repository, Logilica imports completed workflow runs and the work beneath them:

* **Workflow runs** — name (falling back to the workflow identifier when a run has no name), link to the run on GitHub, created and started timestamps, and the resolved completion time
* **Status and conclusion** — the run's `status` and `conclusion` as reported by GitHub
* **Triggering actor** — the person or account that triggered the run
* **Commit and branch** — the head commit and the branch the run executed against
* **Pull request associations** — any pull requests linked to the run
* **Jobs and steps** — the jobs in each run and the steps within them, with their names, links, and timings

## How Logilica Maps the Data

Build outcomes are normalised so that success, failure, and cancelled results are consistent across every CI/CD platform Logilica supports. The values shown match those reported by GitHub.

{% hint style="info" %}
**In-progress runs are skipped.** Only workflow runs that have completed are imported. Runs that are still queued or running are left out until they finish and are picked up on a later scan.
{% endhint %}

## Good to Know

* **Kept in sync automatically.** After the initial import, Logilica refreshes this connection on a regular schedule — you don't need to re-trigger imports.
* **First import covers the last 6 months.** The initial scan imports workflow runs created within the last 6 months. Importing older history requires a configuration change by Logilica — contact support.
* **Release detection flags deployments.** Logilica runs [release detection](/configuration/release-detection.md) over imported builds, flagging the runs that represent deployments so they can power your DORA metrics.
* **There is a cap on imported runs per repository.** Logilica imports up to roughly the most recent 1000 workflow runs per repository at onboarding. Future runs are added to the stored history as they complete.
* **It feeds Build and DORA.** Imported runs power the [Build dashboard](/metrics-and-reports/build.md) (build frequency, reliability, speed, and recovery time) and, once [Release Detection](/configuration/release-detection.md) is configured, the [DORA metrics](/configuration/dora-configuration.md).
* **Push your own build data.** If you run builds that this connector doesn't cover, you can send them via the [Build Data Import API](/advanced/import/build-data.md).