GitHub App Integration

Installation

1. Install the Forgecroft GitHub App on your organization or repository
2. After installation, you are redirected back to Forgecroft which creates a VCS integration record
3. The integration is ready — webhooks are configured automatically

What the GitHub App Provides

Push Webhooks

When you push to a branch, Forgecroft receives the webhook and reads the changed files to keep your system map current. It ingests CI/CD, container, Kubernetes manifest, and governance files as evidence — new and changed Components and Controls appear as pending proposals you review and approve. Pushes never trigger an execution: Forgecroft reads your infrastructure as evidence, it does not run it.

Pull Requests

Pull requests are evaluated by the CI merge gate, which runs inside your own CI runner and posts the verdict as a sticky PR comment. See the CI Gate guide for setup. The verdict can also be delivered to Slack as a decision packet — see Slack Integration.

VCS Integration Record

After installation, Forgecroft creates a VCS integration with:

• provider: github
• installation_id: from the GitHub App installation
• source_repo_url: from the installation context

This integration lets Forgecroft resolve a push or pull request back to the repository it came from.

Related

• CI Gate — evaluate pull requests against your Controls
• Core Concepts — the system map a change is evaluated against