Skip to content

docs: explain pull request verification routing #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wolfiesch merged 3 commits into from
Sep 1, 2026
Merged

docs: explain pull request verification routing #47

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b52fa90
docs: explain pull request verification routing
wolfiesch Sep 1, 2026
b90a1a1
ci: keep exact-head review in shipping gate
wolfiesch Sep 1, 2026
7cb51d6
docs: clarify review freshness check
wolfiesch Sep 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
75 changes: 0 additions & 75 deletions .github/workflows/review-gate.yml
View file
Open in desktop

This file was deleted.

6 changes: 6 additions & 0 deletions docs/verification.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,12 @@ cargo build --release --locked --manifest-path host-rs/Cargo.toml -p agenttab-ho

The workspace checks TypeScript adapters, extension code, installer, OMP adapter, and package builds. The architecture gates cover manifest identity, required and optional permission behavior, RPC schemas, forbidden legacy surface, and Rust IPC framing. They do not operate a real signed-in browser.

## Pull request routing

Pull requests that change only `README.md`, `CHANGELOG.md`, `LICENSE`, documentation files ending in `.md`, `.rst`, or `.txt` under `docs/`, or a top-level `.github/*.md` file use the lightweight CI lane. The classifier still scans added public text for credentials, private paths, session identifiers, and private hosts. Source, manifest, workflow, nested GitHub, executable documentation, mixed, empty, or ambiguous changes use the full cross-platform lane.

Branch protection requires the stable `verify` check. The automatic review ruleset requests a fresh review after every push. Before merging, confirm that the latest automated review commit matches the current pull-request head; if the commits differ, request another review. Unresolved review threads remain merge blockers.

## Live browser evidence

Use a disposable Chrome profile and a disposable test account. Reload the unpacked extension through Chrome's extension UI, then observe the actual surface after every UI action. Exercise:
Expand Down
Loading