---
title: "GitHub integration for LuumenAI"
url: "https://www.luumen.ai/integrations/github/"
entity: SoftwareIntegration
category: "Source control & CI/CD"
audience: "SRE, DevOps, platform engineering, IT operations"
---

# GitHub integration for LuumenAI

Repos, actions, and runbook code as context and as actions.

## What LuumenAI can do with GitHub

LuumenAI connects to GitHub with OAuth 2.0 and exposes 874 tools (470 read-only · 262 write · 142 destructive). Reads answer immediately; writes are shown as a plan and require approval by default, configurable per tool by an administrator.

## Key facts

- Authentication: OAuth 2.0
- Tools available: 874 tools (470 read-only · 262 write · 142 destructive)
- Plan: available on all plans
- Category: Source control & CI/CD

## About GitHub with LuumenAI

Use GitHub as both context and control. LuumenAI reads repos, pipelines, and runbook code to understand a change, then proposes pull requests, triggers jobs, or rolls back releases as approved, audited steps.

## Example tools

Read-only (470 in total):

- `GITHUB_API_ROOT` — Retrieves a map of all top-level GitHub REST API resource URLs and their templates.
- `GITHUB_CHECK_FOLLOWING` — Check if the authenticated user is following a specified person on GitHub.
- `GITHUB_CHECK_IF_GIST_IS_STARRED` — Checks if a gist is starred by the authenticated user.
- `GITHUB_CHECK_IF_PULL_REQUEST_HAS_BEEN_MERGED` — Checks if a specified GitHub pull request has been merged, indicated by a 204 HTTP status (merged) or 404 (not merged/found).
- `GITHUB_CHECK_IF_PULL_REQUEST_MERGED` — Checks if a pull request has been merged by querying the GitHub API.
- `GITHUB_CHECK_IF_USER_CAN_BE_ASSIGNED` — Verifies if a GitHub user can be assigned to issues in a repository; assignability is confirmed by an HTTP 204 (No Content) response, resulting in an empty 'data' field in the response.
- `GITHUB_CHECK_IF_USER_CAN_BE_ASSIGNED_TO_ISSUE` — Checks if a specified GitHub user can be assigned to a given issue within a repository.
- `GITHUB_CHECK_IF_USER_FOLLOWS_ANOTHER_USER` — Checks if a GitHub user `username` follows `target_user`; returns a 204 HTTP status if true, 404 if not or if users are invalid.

Write and destructive (404 in total, approval required by default):

- `GITHUB_ABORT_REPOSITORY_MIGRATION` — Abort a repository migration that is queued or in progress.
- `GITHUB_ACCEPT_REPOSITORY_INVITATION` — Accepts a PENDING repository invitation that has been issued to the authenticated user.
- `GITHUB_ADD_APP_ACCESS_RESTRICTIONS` — Adds GitHub Apps to the list of apps allowed to push to a protected branch.
- `GITHUB_ADD_A_REPOSITORY_COLLABORATOR` — Adds a GitHub user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and…
- `GITHUB_ADD_ASSIGNEES_TO_AN_ISSUE` — Adds assignees to a GitHub issue.
- `GITHUB_ADD_EMAIL_ADDRESS_FOR_AUTHENTICATED_USER` — Adds one or more email addresses (which will be initially unverified) to the authenticated user's GitHub account; use this to associate new emails, noting an email verified for another account will…
- `GITHUB_ADD_FIELD_TO_USER_PROJECT` — Add a custom field to a user-owned GitHub Projects V2 project.
- `GITHUB_ADD_ITEM_TO_USER_PROJECT` — Add an issue or pull request to a user-owned GitHub project.

## Frequently asked questions

### How does LuumenAI connect to GitHub?

Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

### Can LuumenAI change things in GitHub on its own?

Read actions answer immediately. Anything that writes is shown as a plan and requires approval by default, including the 142 actions classified as destructive. Administrators configure that per tool.

### Is there an audit trail?

Every call to GitHub — read or write, approved or declined — is recorded with the actor, the input, and the result.

Full page: https://www.luumen.ai/integrations/github/