The GitHub PR channel

The GitHub PR channel puts regenerated files into your own repository: on every regeneration, Sichta opens a pull request with the changed files. You review, merge, and your normal deploy pipeline takes it from there.

Setup

  1. In the app, open your site → Channel and find GitHub pull request.
  2. Install the Sichta Conformance GitHub App on the repository that deploys your site. It asks for Contents and Pull requests permissions, on the repositories you pick and no others.
  3. GitHub sends you back to a URL ending in installation_id=…. Paste that number into the form.
  4. Choose the repository, the base branch, and the directory that maps to your web root (often public/ or static/, or blank for the repository root). Save.

What a PR looks like

One branch per regeneration, named sichta/conformance-<date>-<set number>, with every file in a single commit — a PR whose history reads "update llms.txt / update llms-full.txt / update security.txt" is harder to review than the diff it represents.

The diff touches only the generated files. The PR body lists them with their sizes and says how many entries still carry a review marker.

If the generated files already match the base branch, no PR is opened at all: an empty pull request only wastes a review.

The trade-off

Files stay in your repo and your review gate. In exchange, an unmerged PR means the live files drift until someone merges — the daily check will tell you, but it cannot merge for you.