Apply fixes as GitHub pull requests

The fix feed ends the 'here's a recommendation, good luck' gap: each item that produces a repo artifact (llms.txt, sitemap scaffold, feed scaffold, JSON-LD instructions) can be applied to your site repository as a pull request. You review and merge on GitHub — Citepath never auto-merges — then verify-applied re-crawls your live domain to confirm the artifact landed.

Connect GitHub

Open a brand's Fix Feed and use the GitHub apply panel. Two connection options are offered depending on how the deployment is configured — either works:

• GitHub App (recommended) — install the Citepath app on just the repo(s) you want PRs on. Permissions are scoped to contents + pull requests, tokens expire hourly, and PRs are authored by the Citepath bot, not you.
• GitHub OAuth — authorize with the repo scope. Simpler, but grants access to all repos your account can reach and PRs appear authored by you.

After connecting, bind the repo that serves the brand's domain (owner/repo). Citepath checks the credential can actually see it before saving.

Apply a fix

Click 'Apply via GitHub PR' on an eligible item. Citepath detects your repo's static convention — public/ for Next.js, Vite, Astro, SvelteKit, Remix, Nuxt, Gatsby; static/ for Hugo — and writes the artifact in the right place on a citepath/fix-* branch. JSON-LD items, where <head> wiring can't be guessed, ship as a labeled docs/GEO-FIXES.md instructions file instead.

If your latest readiness audit found AI crawlers disallowed in robots.txt, the same PR appends additive 'User-agent / Allow: /' groups — it never rewrites or deletes your existing rules.

What the PR says — and what happens after

• The PR body lists every file, links back to the fix item, and states plainly that a human reviews before merge — nothing is auto-merged.
• When you merge the PR on GitHub, the item flips to applied (merge webhook, or mark it manually).
• Applied isn't verified: the fix feed's verify step re-fetches the live artifact from your domain and only then marks the item verified — with the observed response stored as evidence.
• That last step is the closed loop: measure → diagnose → PR → merge → verified on your live site.