PR review quick start
Get your first PR review
Yanib checks supported changes and affected code in the same repository or the connected repositories you explicitly select. Results include consequences, code locations, recommendations, verification, and coverage limits. Reviews are advisory.
1. Connect a GitHub repository
Open PR review setup. Sign in, install or configure the Yanib GitHub App, and choose which repositories it can access. GitHub sign-in and App installation are separate permissions. An organization owner may need to approve the installation; return to the same setup page when approval is granted.
Standard Free supports one connected repository. Your own multi-repository evaluation requires an eligible plan. Check the evaluation options before authorizing additional code. GitLab release workflows remain available, but PR impact review currently requires GitHub.
2. Choose scope and permissions
Enable Analyze pull requests to allow source indexing and review processing. Read the data-processing information first. Enable Post reviews in GitHub separately, or leave it off to preview results inside Yanib. Both choices persist independently.
Same-repository analysis is included. For cross-repo review, connect each target to the same Yanib workspace, enable its analysis, and select it in the source repository’s Scope screen. Selecting B for PRs in A does not enable A for PRs in B. Unselected repositories do not become review context just because they share an organization.
A release, integration, or committed surface file is not required for baseline PR review. Additional dependency families can require identity configuration in advanced setup. Docs PRs, consumer issues, and release publishing have separate controls.
3. Confirm preparation and request a review
The First review screen distinguishes repository access, analysis consent, index preparation, and permission to publish. Index preparation is not the same as complete coverage. Large repositories and unsupported patterns may produce a limited result; Yanib names those limits in the review.
New eligible opened, reopened, ready-for-review, and updated PRs request analysis automatically once enabled. To evaluate an existing PR, choose Load open PRs, paste its GitHub URL, or enter its number. Then confirm Request review. Choosing a PR does not start analysis, and drafts must be marked ready in GitHub first. No test commit or PR is created for you. If you have no suitable open PR, use a normal code change in a test repository or inspect the public review example.
A queued request is not a completed review, and enabling posting is not proof that GitHub received it. Recent attempts show recorded analysis and delivery. Open Impact Review to check the current PR revision, then inspect the advisory review in GitHub. New commits require a fresh result; outdated results are not presented as current.
Why no review appeared
- Repository missing: confirm the active workspace, GitHub sign-in, App repository selection, and organization approval. Reconnect only the intended repository.
- Analysis off: connecting code does not by itself grant every optional review or write permission. Check saved Scope settings.
- Preparing or unavailable index: refresh readiness. A release-history scan is not the PR index. Background retries can recover failed attempts; contact support if the state persists.
- No eligible event: enabling a switch is not a PR event. Request an existing open PR manually, or push a normal new commit. A draft can become eligible when marked ready for review.
- Result only in Yanib: posting may be off, the service may be paused, or the App may lack write permission. Check both the saved switch and the recorded delivery.
- Outdated result: the PR base or head changed, or selected scope changed. Request a new review. Access failures hide results until the current revision can be verified.
- No findings or incomplete coverage: neither is a guarantee that a change is safe. Read which repositories and patterns were checked, and retain your normal tests and human review.
Pause, disconnect, or delete
Turn posting off to stop GitHub publication while retaining analysis. Turn analysis off to stop PR processing. To remove repository access, disconnect the repository in Repositories. Index removal and stored-data cleanup run separately; an off switch is not confirmation that retained data has already been erased. GitHub comments already posted are external copies. See the retention and deletion details or contact support@yanib.dev.