feat: create a web page to explain the pr for prs labeled with preview#7025
preview#7025Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #7025 +/- ##
==========================================
- Coverage 80.07% 79.69% -0.39%
==========================================
Files 596 596
Lines 66444 66444
==========================================
- Hits 53206 52953 -253
- Misses 10096 10365 +269
+ Partials 3142 3126 -16 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
PR previewUpdated for commit 4804c6d. |
|
This PR is considered to be stale. It has been open 20 days with no further activity thus it is going to be closed in 7 days. To avoid such a case please consider removing the stale label manually or add a comment to the PR. |
…ent steps 🔒 Scanned for secrets using gitleaks 8.28.0
… section 🔒 Scanned for secrets using gitleaks 8.28.0
🔒 Scanned for secrets using gitleaks 8.28.0
🔒 Scanned for secrets using gitleaks 8.28.0
🔒 Scanned for secrets using gitleaks 8.28.0
…review.yaml 🔒 Scanned for secrets using gitleaks 8.28.0
…yment in ai-preview.yaml 🔒 Scanned for secrets using gitleaks 8.28.0
…ut guidelines 🔒 Scanned for secrets using gitleaks 8.28.0
🔒 Scanned for secrets using gitleaks 8.28.0
…itions for PR previews 🔒 Scanned for secrets using gitleaks 8.28.0
a86e3eb to
7d2db22
Compare
🔒 Scanned for secrets using gitleaks 8.28.0
| run: | | ||
| set -euo pipefail | ||
| mkdir -p review-work | ||
| codex exec --dangerously-bypass-approvals-and-sandbox \ |
There was a problem hiding this comment.
This seems a bit dangerous, why do we need to bypass network restrictions?
There was a problem hiding this comment.
GitHub-hosted runners block bubblewrap's network. So we had to bypass the sandbox.
There was a problem hiding this comment.
Using this, this prevents network access and also adds other restrictions, like removing superuser privileges.
🔒 Scanned for secrets using gitleaks 8.28.0
…ndboxing 🔒 Scanned for secrets using gitleaks 8.28.0
🔒 Scanned for secrets using gitleaks 8.28.0
…preview 🔒 Scanned for secrets using gitleaks 8.28.0
🔒 Scanned for secrets using gitleaks 8.28.0
… validation steps 🔒 Scanned for secrets using gitleaks 8.28.0
…and improve job execution 🔒 Scanned for secrets using gitleaks 8.28.0
…cate TOML keys 🔒 Scanned for secrets using gitleaks 8.28.0
…event duplicate keys and streamline subagent execution 🔒 Scanned for secrets using gitleaks 8.28.0
Description
Adds an opt-in GitHub Actions workflow that generates an AI-authored, visual review site for a PR and publishes it to GitHub Pages, gated by an ai-preview label.
Why
Reviewing an unfamiliar PR in an unfamiliar area of the codebase is slow. This generates a single self-contained page — architecture/sequence/state diagrams, a file walkthrough with annotated hunks, a risk
grid, and a review checklist — so a reviewer can understand the change by scanning before reading the diff.
How it works
The site is built by a sequential pipeline of four specialised Codex subagents (Codex CLI on Azure Foundry), each a separate
codex execwith a focused prompt from.github/codex/agents/(sharedconventions in
_shared.mdare prepended to every stage). Stages hand off through areview-work/scratch directory that never leaves the runner — onlyreview-site/is deployed.analyze.mdreview-work/analysis.json— structured facts (tl;dr, components, flows, data shapes, per-file summaries). Only stage that explores the repo broadly.diagrams.mdreview-work/diagrams/*.svg+diagrams.jsonmanifest — hand-authored SVGs, changed elements in accent color.risks.mdreview-work/risks.json— adversarial pass: risks with severity, review checklist, testing assessment.assemble.mdreview-site/index.html— single self-contained page; presentation only, no fresh analysis.Required configuration
How to use
Add the ai-preview label to a PR. Re-add it to refresh the preview after new commits (pushes alone don't rebuild). Close/merge the PR to tear the preview down.
Linear Ticket
Security