> For the complete documentation index, see [llms.txt](https://docs.sealsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealsecurity.io/integrations/github.md).

# GitHub

<figure><img src="/files/TTXSj6klpPbwfdNYcZm1" alt="GitHub" width="100"><figcaption></figcaption></figure>

Seal ships two GitHub-specific components that customers install separately. They cover different parts of the integration with GitHub:

* **The Seal GitHub App.** A GitHub App you install on your organization (or selected repositories) that gives Seal source-side context: discovered packages from your default branch, automatic pull-request creation for `.seal-actions.yml` updates, and Sealing-Rule-driven PRs.
* **The Seal GitHub Action.** A GitHub Actions step you reference in your workflow YAML to invoke the Seal CLI inside a GitHub-hosted (or self-hosted) runner.

Both are independent components. You can install one without the other; many customers do.

## In this chapter

* [The Seal GitHub App](/integrations/github/github-app.md): what it does, what permissions it needs, and where it appears in the Seal UI.
* [The Seal GitHub Action](/integrations/github/github-action.md): inputs, outputs, action versions, examples.

## Related

* [Connecting GitHub](/discovering/connecting-source-control/github.md): the source-control connection how-to that walks through installing the GitHub App.
* [Integrating with GitHub Actions](/setup-apps-os/cli-in-cicd/github-actions.md): the day-1 setup how-to that walks through using the Action in a workflow.
* [Working with Seal Apps under Local](/using-platform/working-with-seal-apps/local.md): how the App's automatic-PR feature is used day-to-day in the Local deployment method.