Install the Warestack GitHub App on the organization that owns the in-scope repositories. Admin access is required for the org install.

1. Sign in at warestack.com  with GitHub.
2. Install the app and select the repositories Warestack should govern.
3. Confirm the GitHub identity that will be the individual owner on each in-scope repo.

Warestack reads pull requests, reviews, review threads, checks, workflow runs, deployments, deployment reviews, and branch protection. Those events power Overview, Events, PR stacks, rules, and chains.

The Warestack Rules check is published on the pull request. It is not a merge gate until branch protection requires it. Warestack shows current protection and links to GitHub; protection remains managed there.

For an eligible blocking finding, the current check can provide a revision-bound /warestack ack <violation_id>:<64-hex-reference> --reason <reason> command. A GitHub user with Maintain or Admin access can post that exact command as a standalone pull-request comment; a Warestack account is not required. The command cannot waive incomplete evidence.

First-run repository insights can use recent activity to suggest a bounded starting set. They do not turn inferred GitHub signals into Warestack ticket associations. Linear candidates come only from deliberate branch/title references, a terminal Refs: trailer, an explicit Linear issue URL, or provider attachment; Warestack reports linkage only after persistence.

Connect Slack and Linear next so live cards, DMs, and ticket association have somewhere to go.