GitHub

Reference for the two GitHub components Seal ships, the Seal GitHub App and the Seal GitHub Action.

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: what it does, what permissions it needs, and where it appears in the Seal UI.

• The Seal GitHub Action: inputs, outputs, action versions, examples.

Related

• Connecting GitHub: the source-control connection how-to that walks through installing the GitHub App.

• Integrating with GitHub Actions: the day-1 setup how-to that walks through using the Action in a workflow.

• Working with Seal Apps under Local: how the App's automatic-PR feature is used day-to-day in the Local deployment method.