Skip to main content
The GitHub integration connects your repositories to Atmet so that engineering events — a new issue, an opened pull request, a branch change — can kick off automated workflows across your entire tool stack. Use it to route issues to the right team member the moment they’re filed, remind reviewers about open PRs that have gone stale, post deployment summaries to Slack, or keep your project management tools in sync with what’s happening in code. Atmet treats your GitHub activity as a first-class event stream that your AI agents can act on in real time.

​
Prerequisites

Before connecting GitHub, make sure you have:
  • A GitHub account (personal or organization)
  • Access to the repositories you want to automate (Atmet will only be able to interact with repos your account has access to)
  • For organization repositories: organization members may need owner approval to install new OAuth apps, depending on your org’s policy

​
Connecting GitHub

1

Open Integrations

In the Atmet sidebar, navigate to Integrations and find GitHub in the list.
2

Click Connect

Click the Connect button. You’ll be redirected to GitHub’s OAuth authorization page.
3

Authorize Atmet

Review the requested permissions and click Authorize. If you’re a member of GitHub organizations, you can also grant access to specific org repositories at this step.
4

Confirm the connection

GitHub redirects you back to Atmet. A green Connected badge confirms your account is linked and ready to use in workflows.
If you need to automate repositories belonging to a GitHub organization, ask your organization owner to approve the OAuth app, or use a personal access token with repo scope if your organization requires it.

​
Triggers

GitHub supports a rich set of triggers covering the full development lifecycle. Below are the most commonly used trigger categories.
Use these triggers when you want to auto-assign, auto-label, or notify a team member every time an issue is filed or updated — especially useful for on-call routing and bug triage.
Use these triggers when you want to notify reviewers, run a checklist validation, post a summary to Slack, or create a linked task in Jira the moment a PR is opened or updated.

​
Actions

GitHub provides a comprehensive set of actions. Below are the most frequently used categories.

​
Workflow ideas

Automated issue triage

Trigger on new issues. Use an AI step to classify the issue type (bug, feature request, question) and automatically apply the correct label, assign to the right team, and post a triage summary as a comment.

PR review reminder

Trigger on new pull requests. Wait 24 hours, then check if the PR has been reviewed. If not, send a Slack DM to the assigned reviewers with a direct link to the PR.

Release notes generator

Trigger on a new release creation. Use the Generate release notes action to build a changelog from recent commits, then post the summary to a Slack channel and a Notion page.

Cross-tool issue sync

Trigger on new issues labeled customer-reported. Automatically create a linked Jira ticket or Asana task with the same title and description, then add a comment to the GitHub issue with the ticket link.

​
Limitations and notes

GitHub’s REST API enforces rate limits of 5,000 requests per hour for authenticated requests. High-frequency workflows that poll or list resources in large repositories may approach this limit. Where possible, use triggers instead of scheduled polling.
When creating issues or PRs programmatically, use the body field to include context from upstream workflow steps — for example, a Slack message body, a customer email summary, or an AI-generated description. Rich context makes automated issues much more actionable for your team.
The Create an issue comment action works on both issues and pull requests — they share the same comment API in GitHub. Use the issue or PR number as the reference in your workflow step.
Yes. During the OAuth flow, GitHub will show a list of organizations you belong to. Click Grant next to any organization to authorize Atmet for that org’s repositories. Organization owners may need to approve the OAuth app before access is granted — they’ll receive a request notification in their GitHub settings.