Skip to main content
Connect your GitHub repositories to NOFire for investigations that understand both your infrastructure behavior and your code changes. Works with all GitHub plans: Free, Pro, Team, and Enterprise Cloud.

​
How NOFire Uses GitHub

NOFire connects via GitHub App for secure, automated access to your repositories during investigations: Automatic Token Management
  • Uses GitHub’s native app authentication
  • Tokens refresh automatically without manual intervention
  • No personal access tokens to manage or expire
Investigation Context
  • Analyzes relevant source code when investigating incidents
  • Reviews recent commits and pull requests
  • Identifies code patterns that correlate with system behavior
  • Connects telemetry signals (logs, metrics, traces) with code changes
Ask Questions Across Your Stack
  • “Did recent deployments cause this latency spike?”
  • “Which code changes happened before the error rate increased?”
  • “Show me commits touching the authentication service this week”

​
Setup Steps

  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 incident investigations.

​
Automatic Change Tracking

NOFire monitors code activity through GitHub webhooks to build a timeline of changes. This powers faster root cause analysis by connecting code events with system behavior. Change Events Code Pushes
  • Branch commits with author and timestamp
  • Commit messages and SHA references
  • Batch size (number of commits per push)
Pull Requests
  • When PRs open and merge
  • Author and merger identity
  • Target branches
Deployments
  • Environment targets (staging, production, etc.)
  • Version references and commit SHAs
  • Deployment status progression
Releases
  • Published releases with tags
  • Version identifiers
Investigation Benefits NOFire builds a causal timeline connecting:
  • Code commits → service deployments → incident timing
  • Pull request merges → behavior changes in production
  • Release versions → specific error patterns
During investigations, ask:
  • “What code shipped to production before this started?”
  • “Which commits touched the payment service today?”
  • “Did any deployments happen during the latency spike?”
Webhook data is processed securely and retained for incident correlation. NOFire has read-only access and cannot modify code or trigger GitHub actions.

​
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 during investigations 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 configurations
  • Trigger workflows or actions
You can verify the exact permissions during GitHub App installation.

​
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.