> 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.md).

# GitHub

The GitHub connector imports pull requests, commits, code reviews and releases so your delivery, review and DORA metrics reflect what actually happens in your repositories.

## Authentication

Logilica connects to GitHub in one of three ways:

* **OAuth** — authorise Logilica through GitHub's standard consent screen. Logilica only reads the relevant data and never stores your password.
* **Personal Access Token (PAT)** — supply a token where OAuth is not available or where token-based access is preferred. The token needs the `repo`, `user:read`, and `user:email` scopes.
* **GitHub App installation** — install the Logilica GitHub App on your organisation. This is the recommended option for organisation-wide access and for **GitHub Enterprise** and **self-hosted GitHub**.

For self-hosted or Enterprise GitHub, provide your instance URL when installing the connector. Logilica routes all API calls to your instance instead of public GitHub.

See [Connecting Tools](/integration/connecting-tools.md) for the general installation flow.

## What's Imported

For each connected repository, Logilica imports:

* **Pull requests** — title, description, author, branch names, created/updated/closed/merged timestamps and the merger
* **Commits** on each pull request, including author, committer, commit message and authored/committed times
* **Pull request reviews** — reviewer, submission time, the review outcome, and the files each review touched
* **Releases** — name, tag, target commit, author and publish date (see [How Logilica Maps the Data](#how-logilica-maps-the-data))
* **Contributor identities** — name, email and username for every author, reviewer and merger.

When the connector is installed against an organisation, Logilica also discovers all organisation members and creates contributor identities for them, not only the people who appear directly on pull requests.

{% hint style="info" %}
Optional connector settings add **GitHub Actions** build data, **GitHub Copilot** usage data and **team synchronisation**. These are toggled on the connector's configuration page after installation. See [Connecting Tools](/integration/connecting-tools.md#connector-settings).
{% endhint %}

## How Logilica Maps the Data

### Pull request state

Logilica tracks each pull request through its lifecycle — open, reviewed, approved, merged or closed — combining GitHub's status with review activity. These states feed the review and delivery metrics.

### Review lifecycle

Logilica captures who reviewed each pull request, which files they reviewed, approvals, and review timing. A pull request author's reviews on their own pull request are not counted as review activity.

### Release detection

Logilica detects releases two ways, controlled by your [Release Detection](/configuration/release-detection.md) settings:

* **GitHub Releases** — when release detection is set to use repository releases, Logilica imports published releases directly from GitHub, including the tag, target commit and author.
* **Pull request patterns** — Logilica can also treat pull requests whose title matches your configured release pattern as releases.

Release data feeds [DORA metrics](/configuration/dora-configuration.md) and the [Build dashboard](/metrics-and-reports/build.md).

### Linking pull requests to tickets

Logilica recognises issue keys in commit messages, pull request titles and branch names to connect code changes to planning work. See [Linking Pull Requests and Tickets](/integration/linking-pull-requests-and-tickets.md) for how this works and how to format references.

## 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.** Only pull requests updated in the last 6 months are imported on the first scan. Pull requests created more than 6 months ago that are already closed are skipped even if recently touched. Importing older history requires a configuration change by Logilica — contact support.
* **Self-hosted and Enterprise GitHub are supported** via the GitHub App installation with a custom instance URL.
* **Commit timing handles cherry-picks.** Logilica chooses commit timestamps so cherry-picked commits don't distort your statistics.
* **Review comments are counted, not stored verbatim.** Logilica records which files were reviewed and the number of comments, but does not retain the comment text.