GitHub automation
PR scans obey repo access and operator intent. These rules describe exactly when Infiniview triggers, debounces, or skips.
Events that can trigger
Infiniview listens for opened, synchronize, and ready_for_reviewpull request events. Draft PRs are skipped until they’re marked ready for review.
POST /api/github/webhook # GitHub-signed webhook receiverAuto-review scope
Settings can limit automation to specific repositories. Leaving the repo list empty means the installation can run with default settings against any installed repo.
Own PRs only
When enabled, Infiniview compares the pull request author to your connected GitHub username and skips PRs by other authors. Useful for solo developers who only want to review their own work.
Push debounce
synchronizeevents inside the configured debounce window are ignored, so a burst of commits doesn’t start redundant scans. The debounce window applies per PR.
Ignored PRs
@infiniview ignore stores an installation-level skip for that repo and pull request number. Future synchronize events on that PR will not trigger auto-review until the suppression is cleared.
Trusted commands
These commands only run for owners, members, collaborators, or users with write-or-better permission on the repository. Comments from anyone else are ignored.
| Command | Effect |
|---|---|
@infiniview review | Starts a trusted manual PR scan. |
@infiniview ignore | Skips future auto-reviews for that repo + PR number. |
@infiniview help | Replies with the current command list. |
Unsupported apps
If Infiniview can’t run the repository as a supported browser web app, the PR check completes neutrally with an Unsupported App status instead of returning a misleading pass. Coverage gaps are tracked in trust — see Trust & readiness.