Skip to main content
Connect GitHub to NOFire using a GitHub App. Works with github.com (all plans: Free, Pro, Team, Enterprise Cloud) and self-hosted GitHub instances connected through the Edge Proxy.

​
github.com

  1. Visit https://my.nofire.ai/dashboard/connections
  2. Select Connect for GitHub
  3. Authorize NOFire in GitHub when redirected
  4. Choose which repositories to grant access (all repositories or specific ones)
GitHub repository selection screen
  1. Confirm installation
Setup complete. NOFire can now analyze your code during investigations.

​
Self-Hosted GitHub

If your GitHub instance is not publicly accessible, install a GitHub App on it manually and connect it through the Edge Proxy. Same mechanism as the cloud setup — no PATs required. Prerequisites: Edge deployed in your cluster with the Edge Proxy enabled. See On-Prem Connections.

​
1. Register a GitHub App on Your Instance

Log in to your GitHub instance and navigate to Settings > Developer Settings > GitHub Apps > New GitHub App.
  • Homepage URL: https://nofire.ai
  • Enable the following Repository Permissions as Read-only:
    • Contents
    • Commit statuses
    • Deployments
    • Metadata
    • Pull requests

​
2. Collect App Credentials

After creating the app, collect:
  • App ID — shown on the app’s settings page
  • Private Key — generate and download from the app’s settings page
  • Installation ID — install the app in your organization, then get the ID from the URL: github.your-company.com/organizations/<org>/settings/installations/<Installation-ID>

​
3. Store the Private Key as a Kubernetes Secret

​
4. Configure in values.yaml

​
5. Upgrade the Release

NOFire routes GitHub API requests through the Edge Proxy using short-lived installation tokens. Credentials stay inside your cluster.

​
What NOFire Does With Your Repositories

NOFire reads your repositories on demand during investigations to connect code changes with system behavior. During investigations, NOFire can:
  • Read file contents and commit history for relevant services
  • Review recent pull requests and deployment events
  • Identify which code changes correlate with a production change
Via webhooks, NOFire builds a continuous change timeline: This timeline connects code events with infrastructure behavior so you can understand what changed and when. NOFire has read-only access. It cannot push commits, open pull requests, or trigger workflows.

​
Frequently Asked Questions

​
What repository data can NOFire see?

NOFire requests read-only access to:
  • Repository structure and file contents
  • Pull request history (open and closed)
  • Commit details including diffs
  • Repository settings (default branch, topics)
By default, Issues, Projects, and Discussions are not accessible. You control additional scope during installation.

​
Is my source code stored on NOFire servers?

No. NOFire fetches code from GitHub on demand and does not maintain a persistent copy. Exception: Small code snippets shown in investigation results are saved as part of your NOFire investigation history.

​
Can NOFire modify my code?

No. All permissions are read-only. NOFire cannot create or modify commits, open or merge pull requests, change repository settings, or trigger workflows.

​
How do I connect if my GitHub has IP restrictions?

Email [email protected] with your organization details. We’ll provide NOFire’s IP addresses for your allowlist configuration.