Documentation
Drift auto-PR
When a drift alert is approved, open a pull request that re-renders the affected document into your repo.
Last updated May 8, 2026
On Growth and above, Attestly can open a real GitHub pull
request whenever an approved drift change re-renders one of your
documents. The PR contains the new Markdown under compliance/<doc>.md,
ready to merge through your normal review process.
Enabling it
- Go to Dashboard → Settings → Drift handling.
- Toggle Open auto-PRs to your repo.
- The toggle requires at least one teammate with a connected GitHub account in the workspace — that account's token is used to open the PR.
What ships in the PR
- A new branch named
attestly/drift-<short-sha>-<doc-type>. - One file per regenerated document at
compliance/<doc>.md. - A PR title summarising the change (
docs(compliance): regenerate AI Trust Center after drift). - A PR body that links back to the drift alert in your Attestly dashboard.
How it pairs with branch protection
Because the PR is a regular GitHub PR opened by a real user, it inherits
your branch-protection rules: required reviewers, required status checks,
and any CODEOWNERS gates. The drift alert in Attestly stays
pending_external_review until the PR is merged, then transitions to
resolved automatically.
Failure modes
If the PR fails to open (no GitHub token in the workspace, repo write access revoked, conflicting branch already exists), the drift alert is still resolved internally and an in-app notification surfaces the error. The audit log records the failure with the API error code so you can debug.
Disabling auto-PRs
Settings → Drift handling → toggle off. Existing PRs are unaffected.