GitHub Integration

Connect GitHub repositories for code ownership, change tracking, and incident context

Connect your GitHub repositories to AnomalyArmor to monitor code ownership, track changes to data pipelines, and get incident context when alerts fire. AnomalyArmor analyzes your repos for CODEOWNERS files, git blame history, and table references so you can route alerts to the right people.

What AnomalyArmor Does with Your Repos

Once connected and monitored, AnomalyArmor scans your repositories for:

• CODEOWNERS files to map directories and files to team owners
• Git blame data to identify who last modified SQL models, dbt files, and pipeline code
• Table references in SQL files to link code to monitored data assets
• Change correlation to show recent code changes when data quality issues arise

This lets AnomalyArmor automatically suggest alert owners, show who to contact when a table breaks, and provide code-level context for schema changes and freshness incidents.

GitHub App vs OAuth: Which to Choose

AnomalyArmor supports two connection methods. For most teams, the GitHub App is the better choice.

	GitHub App	OAuth App
Setup	One-click install from GitHub Marketplace	Personal OAuth flow
Permissions	Scoped to selected repos only	Access to all repos you can see
Token lifecycle	Auto-refreshing, no expiry	Permanent until revoked
Webhooks	Automatic push event webhooks	Manual per-repo webhook setup
Best for	Teams, production use	Quick personal testing
Identity	Org-level installation	Individual user account

Use the GitHub App if you’re setting this up for a team. It provides granular repo-level permissions and automatic webhook delivery for real-time sync.

Setup: GitHub App (Recommended)

1. Open Git Settings

   Go to Settings > Git Integration in AnomalyArmor.

2. Install GitHub App

   Click Install GitHub App. You’ll be redirected to GitHub to authorize the AnomalyArmor app.

3. Select repositories

   Choose which repositories to grant access to. You can select all repos or pick specific ones.

4. Monitor repos

   Back in AnomalyArmor, your accessible repos appear automatically. Toggle Monitor on for each repo you want to analyze. AnomalyArmor immediately starts scanning for code ownership data.

Setup: OAuth App

1. Open Git Settings

   Go to Settings > Git Integration in AnomalyArmor.

2. Connect with OAuth

   Click Connect with OAuth. You’ll be redirected to GitHub to authorize AnomalyArmor.

3. Monitor repos

   Your accessible repos appear automatically. Toggle Monitor on for each repo you want to analyze.

OAuth tokens are tied to your personal GitHub account. If you leave the organization, the connection breaks. For team setups, use the GitHub App instead.

Monitoring Repos

The Monitor toggle controls whether AnomalyArmor actively analyzes a repository:

• Toggle ON: Creates a repository record and triggers initial analysis (CODEOWNERS parsing, git blame, table reference scanning). The Status column shows progress (Pending, Running, Synced, or Failed).
• Toggle OFF: Pauses monitoring. All existing analysis data is preserved. You can re-enable at any time.

Linking Assets to Repos

For the richest analysis, link your monitored repos to data assets (databases). Click the link icon next to a monitored repo’s status to open the asset linking dialog. This lets AnomalyArmor correlate code changes in the repo with specific tables in your database.

Webhooks

GitHub App

Webhooks are configured automatically when you install the app. AnomalyArmor receives push events in real time and re-analyzes monitored repos when relevant files change (CODEOWNERS, SQL files, dbt models).

OAuth App

OAuth connections do not include automatic webhooks. AnomalyArmor relies on periodic re-sync to pick up changes. You can manually trigger a re-sync from Settings > Git Integration by clicking Re-sync.

FAQ

When should I use the GitHub App vs Connect with OAuth?

Use the GitHub App if any of these apply:

• You are setting up the integration for a team or organization
• You want automatic webhook delivery so AnomalyArmor re-syncs when code changes
• You need fine-grained control over which repos AnomalyArmor can access
• You want a token that refreshes automatically and never expires

Use OAuth if:

• You are testing AnomalyArmor on a personal account and want the fastest setup
• You only need to connect a few repos temporarily
• Your organization has not approved installing third-party GitHub Apps

In most cases, the GitHub App is the better choice. You can always disconnect and switch methods later without losing monitored repository data.

Troubleshooting

”No repositories found” after connecting

• GitHub App: Check that you granted access to at least one repository during installation. Go to your GitHub organization settings, find the AnomalyArmor app under Installed GitHub Apps, and verify the repository access list.
• OAuth: Verify that your GitHub account has access to the repositories you expect. Private repos in organizations may require SSO authorization.

Connection shows “Pending Setup”

The OAuth flow was started but not completed. Click Complete Setup to finish the authorization.

Permissions seem wrong after changing repo access

If you change which repos the GitHub App can access (in GitHub’s settings), click Re-sync in AnomalyArmor to refresh the repository list.

Need to start over

Click Disconnect in the Git Integration settings, then reconnect using either method. Your previously monitored repositories and their analysis data are preserved.

Next Steps

GitHub Actions

Run quality checks in CI/CD

dbt Integration

Connect dbt project metadata

Alert Destinations

Route alerts to the right team

Data Sources

Connect your data warehouse