# GitHub AI integration on Definable

> GitHub is a code hosting platform for version control and collaboration, offering Git-based repository management, issue tracking, and continuous integration features

## What this connects

GitHub is a code hosting platform for version control and collaboration, offering Git-based repository management, issue tracking, and continuous integration features

Vendor: https://github.com/

## Tools available

**846** tools available. First 12:

- `GITHUB_ABORT_REPOSITORY_MIGRATION` — Abort Repository Migration — Tool to abort a repository migration that is queued or in progress. Use when you need to cancel an ongoing migration operation.
- `GITHUB_ACCEPT_REPOSITORY_INVITATION` — Accept a repository invitation — Accepts a PENDING repository invitation that has been issued to the authenticated user.
- `GITHUB_ADD_APP_ACCESS_RESTRICTIONS` — Add app access restrictions — Adds GitHub Apps to the list of apps allowed to push to a protected branch. The branch must already have protection rules with restrictions enabled. This endpoint only works for organization repositories, not personal repositories. Apps must be installed on the repository with 'contents' write permissions.
- `GITHUB_ADD_A_REPOSITORY_COLLABORATOR` — 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 ignore this field), and an invitation may be created or permissions updated directly.
- `GITHUB_ADD_ASSIGNEES_TO_AN_ISSUE` — Add assignees to an issue — Adds assignees to a GitHub issue. This action only adds users - it does not remove existing assignees. Changes are silently ignored if the authenticated user lacks push access to the repository.
- `GITHUB_ADD_EMAIL_ADDRESS_FOR_AUTHENTICATED_USER` — Add email for auth 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 error, while an existing email for the current user is accepted.
- `GITHUB_ADD_FIELD_TO_USER_PROJECT` — Add field to user project — Tool to add a custom field to a user-owned GitHub Projects V2 project. Use when you need to add fields like status, priority, or custom data to organize project items.
- `GITHUB_ADD_ITEM_TO_USER_PROJECT` — Add item to user project — Tool to add an issue or pull request to a user-owned GitHub project. Use when you need to add existing repository items to a project board.
- `GITHUB_ADD_LABELS_TO_AN_ISSUE` — Add labels to an issue — Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
- `GITHUB_ADD_ORG_RUNNER_LABELS` — Add org runner labels — Adds new custom labels to an existing self-hosted runner for an organization; existing labels are not removed, and duplicates are not added.
- `GITHUB_ADD_OR_UPDATE_TEAM_MEMBERSHIP_FOR_USER` — Add or update team membership for a user — Adds a GitHub user to a team or updates their role (member or maintainer), inviting them to the organization if not already a member; idempotent, returning current details if no change is made.
- `GITHUB_ADD_OR_UPDATE_TEAM_PROJECT_PERMISSIONS` — Add or update team project permissions — Adds a classic project to a team or updates the team's permission on it. This endpoint grants or updates permissions for a team on a specific classic project (not Projects V2). The authenticated user must have admin permissions for the project. Both the team and project must belong to the same organization. Requirements: - The project must be a classic project (not GitHub Projects V2) - The authenticated user must have admin permissions on the project - The team and project must be in the same organization - Requires 'admin:org' scope for the authentication token Returns HTTP 204 No Content on success, 403 if project is not an org project, or 404 if the organization, team, or project is not found.

## Auth

Auth schemes: `OAUTH2`. Managed by Definable: `OAUTH2` — no client credentials required from the user.

## How agents use GitHub

Inside a Definable workflow, GitHub is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → GitHub** — the Researcher (GPT-5.5) pulls context from GitHub (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → GitHub** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into GitHub (create record, post message, draft email).
- **Designer / Engineer → Distributor → GitHub** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via GitHub (attach file, open PR comment, post status).

The Verifier checks every GitHub call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- developer tools — https://definable.ai/apps/category/developer-tools/

## Related

- HTML page: https://definable.ai/apps/github/
- Same category (developer tools): https://definable.ai/apps/category/developer-tools/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt