pr-checkup

To check the CI and review status of pull requests linked to GitHub issues, scan the issue bodies for PR references and evaluate each PR's mergeability and CI checks using GitHub CLI commands. This generates a consolidated triage report highlighting PRs needing attention.

Yes, you can triage linked pull requests across multiple repositories. The tool scans issue bodies for PR links and evaluates their review state, mergeability, and CI checks, enabling status aggregation across one or many repositories to accelerate issue triage.

To find pull requests mentioned in an issue body, scan the issue text for PR links. The linked-PR discovery process identifies these references and fetches the corresponding PR details to assess their current review, rebase, and CI status.

The best way to aggregate pull request review and mergeability status for triage is to scan issues for linked PRs and fetch their details via GitHub CLI commands. This retrieves the review state, mergeability, and CI checks to produce an actionable consolidated report.

Yes, you need the GitHub CLI to evaluate pull request CI checks. The tool determines review state, mergeability, and CI checks using GitHub CLI commands to fetch PR details and present a consolidated report for issue triage.

You should scan issues for linked pull requests during triage when you need to assess the review, rebase, and CI status of referenced PRs. This discovers linked PRs across repositories and generates a concise report highlighting PRs needing immediate attention.