dunops.com/Docsbeta

Integrations

GitHub

Dun reads your GitHub repositories — metadata, branches, and file contents — so deploy flows can fetch the right commit. It never pushes code unless you approve a write.

Connect with an API tokenCode3 products

Note

Every mutating action — a deploy, a scale, a secret rotation, a DNS change — surfaces a plan in chat first. Dun never touches your GitHub resources until you approve it.

How to connect

Connect once from Integrations GitHub, then toggle on the products you want Dun to manage.

1

Step 1

Open GitHub → Settings → Developer settings → Personal access tokens.
2

Step 2

Create a fine-grained token with `repo` (read) scope on the orgs you want DunOps to see.
3

Step 3

Paste the token below and click Connect.

Where to get credentials: https://github.com/settings/tokens?type=beta

What Dun can do

Each product below is something you can turn on. The examples are real prompts you can type in a chat thread.

Repositories

Read metadata for repos in the orgs you connect — names, default branch, visibility, latest commit.

Type in a chat thread
List my repositories
What's the latest commit on main in my storefront repo?
Which branch is my api repo deploying from?
PermissionRequiredWhat it does
List organizationsYesDiscover which orgs Dun can see.
List repositoriesYesNames, default branch, and visibility of each repo.
Read repo file treeOptionalResolve which files exist on a branch — never fetches diffs.

Actions

See run history and statuses for the repos DunOps already reads. Read-only — never triggers runs.

Type in a chat thread
Did the last GitHub Actions run on main pass?
PermissionRequiredWhat it does
Read workflow run statusYesSurface success/failure of recent CI runs.

Webhooks

Receive push, deployment-status, and release events so DunOps can react in chat.

Type in a chat thread
Show me my GitHub webhooks
PermissionRequiredWhat it does
Receive repository webhooksYesInbound events only — DunOps never writes back to your repos.

Next steps