Integrations

GitHub

Link a GitHub repository to a website to see its successful production deploys and published releases on the website's charts. Investigations use the same repository to connect traffic and error changes to the code that shipped.

Install the GitHub App

Charts read deploys and releases through the Databuddy GitHub App. Open Organization settings → Integrations → GitHub and choose Connect, then install the App on the GitHub account or organization that owns your repositories and give it access to the ones you want to link.

The App only reads: repository contents, deployments, issues, metadata and pull requests. It can't change anything in GitHub.

Signing in with GitHub lets you pick repositories to link, but it doesn't put deploys on charts. Only the App does. If a linked repository is outside the App's reach, Databuddy says so when you link it and on the repository's row, with a button to install the App.

Under Repositories on the GitHub page, choose a repository for each website, or select Manual and type it as owner/repo.

What shows on charts

  • Production deploys: GitHub deployments that succeeded in an environment named like production, such as production, Production – web or prod-eu. Environments named like previews, staging or pre-production don't count. A deploy shows when it first succeeded, titled with its commit's message and environment. A deploy that failed after succeeding doesn't show.
  • Releases: published releases. Drafts and prereleases don't show.

Hover a marker to see what it is. Select one to open it on GitHub. When markers sit close together, they share a numbered pill; select it to list just those, newest first.

Choose environments for each website

A repository that deploys several apps, such as a monorepo, may deploy many times a day to environments a website doesn't care about. Select Chart markers next to the linked repository to choose which production environments' deploys that website shows, and whether it shows releases. Each environment is listed with its deploys in the last year.

By default a website shows every production environment, including ones added later. Each website linked to the same repository keeps its own choice.

How far back markers reach

Markers cover up to the last 365 days. On very busy repositories GitHub may not send every older deploy in time; the chart then says the date deploys and releases show from.

How soon a new deploy appears

Databuddy asks GitHub for deploys and releases when charts load and keeps them for about 10 minutes, so a new deploy appears within about 10 minutes. If GitHub doesn't respond, the last markers keep showing; when there are none yet, the chart says why.

Markers are read-only and private

Deploys and releases come from GitHub, so they can't be edited or deleted in Databuddy. They show only to members of your organization, never on a public dashboard.

The API's annotations.list and the MCP list_annotations tool include them with the source github_deployment or github_release and their GitHub link. Updating or deleting one is refused. annotations.githubMarkers and the github field of list_annotations say how far back they reach.

How is this guide?