Git overview
Chart repositories, commits, pull requests, issues, releases, tags, branches, contributors and pipeline runs from GitHub, GitLab, Gitea, Bitbucket and Azure DevOps, read-only, in one set of columns.
A Git connection reads analytics data from a hosted code forge with a read-only token. Every forge reads into the same tables and columns, so a chart of commits per week or pull request lead time works the same on GitHub, GitLab, Gitea, Bitbucket or Azure DevOps.
Preview
Git connections are in Preview, and the Git tile in New connection
carries a Preview badge. They are not enabled by default on xentropy.ai:
contact support@xentropy.ai to request access. Until a forge is enabled for
your account it is not offered in the forge selector, and its reads fail
with PROVIDER_DISABLED.
What you can chart
- Delivery: commits per week, by repository or author; pull requests opened, merged and closed; time from open to merge.
- Work tracking: issues (Azure DevOps work items) opened and closed, by type, label or assignee.
- Releases: release cadence, tags and pre-releases over time.
- CI health: pipeline runs by status and conclusion, run duration, failure rate per branch.
- Inventory: repositories with their stars, forks, open issues, default branch and last push; branches and protected branches.
Forges and hosts
Git connections reach only the hosted platforms below. Self-hosted servers (GitHub Enterprise Server, self-managed GitLab, your own Gitea or Forgejo instance, Azure DevOps Server) are not supported yet, and the form has no server address to enter.
| Forge | Host Xentropy calls | Credential |
|---|---|---|
| GitHub | api.github.com | Fine-grained personal access token |
| GitLab | gitlab.com | Personal, group or project access token with read_api |
| Gitea | gitea.com | Access token with read permissions |
| Bitbucket | api.bitbucket.org | Atlassian API token with scopes, or an access token |
| Azure DevOps | dev.azure.com | Organization-scoped personal access token |
GitHub
Fine-grained token with read-only repository permissions.
GitLab
gitlab.com projects with a read_api token.
Gitea
gitea.com repositories with a read-only access token.
Bitbucket
Bitbucket Cloud with a scoped API token or an access token.
Azure DevOps
Azure Repos, work items and builds with an organization-scoped token.
Each forge's connection can call only the read endpoints Xentropy needs on that forge's own host, so no IP allowlist is needed.
Read-only by design
- Every guide asks for read-only permissions only. Xentropy never asks for write or admin scopes.
- Xentropy sends only read requests. The one exception is Azure DevOps work
items, which are found with a WIQL query (a read sent as
POST). - Tokens are encrypted at rest, sent only in request headers to the forge's API, and never shown again after you save them.
- Redirects are never followed. A repository that moved or was renamed
fails with
NOT_FOUNDuntil you select its new name. - Xentropy reads on a schedule or on demand. It does not install webhooks.
Connect a forge
For GitHub, GitLab and Bitbucket, a Connect with … sign-in button may appear above the token fields. It appears only when sign-in with that forge is available for your account; otherwise use a token.
Dataset options
| Option | Applies to | Default |
|---|---|---|
| Resource | All | — |
| Repositories | Everything except repositories | Required: 1 to 20 repositories per dataset, from the connection's selection |
| Branch | commits | The default branch |
Date range (since, until) | commits, pull_requests, issues, pipeline_runs | The last 90 days |
| State | pull_requests (open, closed, merged), issues (open, closed) | All |
Commits are filtered on committed_at; pull requests, issues and pipeline
runs on created_at. The range includes since and excludes until.
closed never includes merged pull requests, so open, closed and merged split
the set on every forge.
Tables and columns
Every table except repositories starts with repository, the repository's
full name (owner/name; for Azure DevOps project/repository). Types are
string, number, boolean and datetime (UTC). A column the forge cannot fill is
empty (null); each forge's guide lists them under Columns left empty.
extra holds the forge's own fields as a JSON object. It is off by default.
repositories
One row per repository the connection can read.
| Column | Type | Notes |
|---|---|---|
id | string | The forge's id |
full_name | string | Row key |
name | string | |
owner | string | Owner, group, workspace or project |
description | string | |
visibility | string | public, private or internal |
default_branch | string | |
fork | boolean | |
archived | boolean | |
language | string | |
stars | number | |
forks | number | |
open_issues | number | |
size_kb | number | |
created_at | datetime | |
updated_at | datetime | |
pushed_at | datetime | Last push |
web_url | string | |
extra | string | JSON object, off by default |
commits
One row per commit on the branch, in the date range.
| Column | Type | Notes |
|---|---|---|
repository | string | |
sha | string | Row key, with repository |
message | string | First line |
author_login | string | The author's forge handle |
author_name | string | Personal data |
author_email | string | Personal data |
authored_at | datetime | |
committer_name | string | Personal data |
committer_email | string | Personal data |
committed_at | datetime | Date range column |
parents | number | 2 or more for merge commits |
additions | number | Lines added |
deletions | number | Lines deleted |
web_url | string | |
extra | string | JSON object, off by default |
pull_requests
Pull requests (GitLab merge requests), created in the date range.
| Column | Type | Notes |
|---|---|---|
repository | string | |
number | number | Row key, with repository |
id | string | |
title | string | |
state | string | open, closed or merged |
draft | boolean | |
author_login | string | |
source_branch | string | |
target_branch | string | |
created_at | datetime | Date range column |
updated_at | datetime | |
closed_at | datetime | |
merged_at | datetime | |
additions | number | Lines added |
deletions | number | Lines deleted |
changed_files | number | |
comments | number | |
web_url | string | |
extra | string | JSON object, off by default |
issues
Issues (Azure DevOps work items), created in the date range. Pull requests are never counted as issues.
| Column | Type | Notes |
|---|---|---|
repository | string | |
number | number | Row key, with repository |
id | string | |
title | string | |
state | string | open or closed |
type | string | issue, or the Azure DevOps work item type |
author_login | string | |
assignee_login | string | |
labels | string | JSON list |
created_at | datetime | Date range column |
updated_at | datetime | |
closed_at | datetime | |
comments | number | |
web_url | string | |
extra | string | JSON object, off by default |
releases
| Column | Type | Notes |
|---|---|---|
repository | string | |
id | string | Row key, with repository |
tag | string | |
name | string | |
draft | boolean | |
prerelease | boolean | |
author_login | string | |
created_at | datetime | |
published_at | datetime | |
web_url | string | |
extra | string | JSON object, off by default |
tags
| Column | Type | Notes |
|---|---|---|
repository | string | |
name | string | Row key, with repository |
commit_sha | string | The tagged commit |
tagged_at | datetime | |
extra | string | JSON object, off by default |
branches
| Column | Type | Notes |
|---|---|---|
repository | string | |
name | string | Row key, with repository |
commit_sha | string | Head commit |
protected | boolean | |
default | boolean | The repository's default branch |
extra | string | JSON object, off by default |
contributors
| Column | Type | Notes |
|---|---|---|
repository | string | |
login | string | Row key, with repository |
name | string | Personal data |
email | string | Personal data |
contributions | number | Commits: all time where the forge counts them, or in the date range when counted from commits |
extra | string | JSON object, off by default |
pipeline_runs
CI runs (GitHub and Gitea Actions, GitLab pipelines, Bitbucket Pipelines, Azure Pipelines builds), created in the date range.
| Column | Type | Notes |
|---|---|---|
repository | string | |
id | string | Row key, with repository |
name | string | Pipeline or workflow |
run_number | number | |
status | string | queued, in_progress or completed |
conclusion | string | success, failure, cancelled, skipped, or empty while running |
branch | string | |
commit_sha | string | |
event | string | What triggered the run |
actor_login | string | Who triggered it |
created_at | datetime | Date range column |
started_at | datetime | |
finished_at | datetime | |
duration_s | number | Seconds |
web_url | string | |
extra | string | JSON object, off by default |
Support by forge
Yes means the forge's API has the resource. From commits means
Xentropy counts contributors from the commits in the date range (by login,
else e-mail, else name), because the forge has no contributors list. No
means the forge has no such data: choosing it fails with VALIDATION_FAILED
before any request is sent.
| Resource | GitHub | GitLab | Gitea | Bitbucket | Azure DevOps |
|---|---|---|---|---|---|
repositories | Yes | Yes | Yes | Yes | Yes |
commits | Yes | Yes | Yes | Yes | Yes |
pull_requests | Yes | Yes | Yes | Yes | Yes |
issues | Yes | Yes | Yes | No (issue tracker API removed) | Yes (project work items) |
releases | Yes | Yes | Yes | No | No |
tags | Yes | Yes | Yes | Yes | Yes |
branches | Yes | Yes | Yes | Yes | Yes |
contributors | Yes | Yes | From commits | From commits | From commits |
pipeline_runs | Yes | Yes | Yes | Yes | Yes |
Where a forge has no releases, read tags instead.
Personal data
Commit author and committer names and e-mails, and contributor names and
e-mails, are marked Personal data in the field picker and are off by
default. Logins are public handles and are not marked. If you select a
personal data field, the dataset is marked as containing personal data
(containsPii). The API and agents must confirm this with
containsPii: true, otherwise the selection is refused.
Limits and refresh
Every read is bounded, and a read either returns complete data or fails.
| Limit | Value |
|---|---|
| Pages per read | Free 100, Pro 600 (shared by all repositories in the dataset) |
| Rows per page | 100 on GitHub, GitLab and Azure DevOps; 50 on Gitea and Bitbucket |
| Rows per read | 50,000 |
| Data per read | 5 MiB |
| Read deadline | 30 s interactive, 300 s scheduled |
| Repositories per dataset | 20 repositories |
| Repositories per connection | 100 repositories, or every repository the token can read |
| History window | The last 90 days unless you set the range |
A history resource on a busy repository can need many pages: on the Free
plan, 100 pages of 100 commits is about 10,000 commits per read (5,000 on
Gitea and Bitbucket). A read over
the limits fails with LIMIT_EXCEEDED or BUDGET_EXCEEDED; narrow the date
range or the repositories, or upgrade to Pro.
Rate limits
Xentropy follows each forge's rate limit headers and pauses before the limit
is reached. Limits are counted per token, so other tools that share the token
share its budget. If the forge asks Xentropy to wait longer than the read's
deadline, the read fails with RATE_LIMITED and details.retryAt says when
the forge will accept requests again. Scheduled refreshes of that connection
wait until then, then run again by themselves. A failed read never replaces
earlier data: charts keep their last capture.
Errors
| Code | Cause | What to do |
|---|---|---|
PROVIDER_ACCESS_DENIED, stage auth | The forge rejected the token (HTTP 401): expired, revoked or mistyped | Create a new token and choose Replace configuration |
PROVIDER_ACCESS_DENIED, stage permissions | A permission is missing (HTTP 403). details.missingScopes names it | Add the permission to the token, or create a new one, then test again |
NOT_FOUND | The repository does not exist, moved or was renamed, or the token cannot see it (HTTP 404 or a redirect) | Check the name on the forge, grant the token access, or select the new name |
RATE_LIMITED | The forge's rate limit is used up (HTTP 429, or 403 with rate limit headers) | Retry after details.retryAt; scheduled refreshes wait by themselves |
VALIDATION_FAILED | The forge has no such resource, or the options are invalid | Choose a supported resource; see the support table |
PERMISSION_DENIED | The repository is not in the connection's selection | Add it to the connection, or choose a selected repository |
INCOMPLETE_DATA | The forge's paging could not be proven complete, or Azure DevOps has 20,000 or more work items | Retry, or narrow the date range |
LIMIT_EXCEEDED, BUDGET_EXCEEDED | More pages, rows or time than the plan allows | Narrow the date range or repositories, or upgrade to Pro |
PROVIDER_UNAVAILABLE | The forge failed (HTTP 5xx) or could not be reached | Retry later |
PROVIDER_DISABLED | The forge is not enabled for your account | Contact support |
Agents
An agent reads a Git connection with an API key that has connections:read
or git:read. Datasets use the git resource: resource, repositories,
and optionally branch, since, until, state, fields and
containsPii. Creating a connection needs connections:manage, as for every
kind; see Connections.
GitHub data and the OpenAPI preset
For GitHub data, use a Git connection: it gives typed tables for repositories, commits, pull requests, issues and workflow runs, with repository selection, personal data off by default and a read-only token. The OpenAPI connection's GitHub preset stays for other GitHub API endpoints and returns their raw JSON. Existing OpenAPI GitHub connections keep working; nothing is migrated.
OpenAPI
Import an OpenAPI 3.0, 3.1 or 3.2 specification, bind GET operations with pagination and field selection, and use the GitHub, Stripe and Docker Hub presets.
GitHub
Connect github.com with a read-only fine-grained personal access token and read repositories, commits, pull requests, issues, releases and Actions runs.