Paginate PR reviews fetch in Community Review Labeler (https://github.com/bazelbuild/bazel/pull/30359) ## Problem The hourly Community Review Labeler queried each PR's reviews without pagination, so it only received the first page (30 reviews). Because the endpoint lists reviews oldest-first and the script selects the latest trusted review, PRs with more than 30 reviews could be labeled from stale data. A simple `--paginate` addition has a second edge case: if a later page fails, `gh api` may already have emitted earlier pages. Treating that partial output as complete could still produce an incorrect label decision. ## Fix - Fetch every review page with `gh api --paginate`. - Fail closed when any page fails: log the PR number and skip its label update. - Preserve the existing newline-delimited output consumed by the downstream `jq -s` selection. ## Verification - `bash -n .github/scripts/community_review_labeler.sh` - `shellcheck .github/scripts/community_review_labeler.sh` - Behavioral harness covering: - successful multi-page output selects the newest trusted review; - empty review history causes no update; - a later-page failure after partial output causes no label mutation. - Verified pagination against a real PR with `per_page=1`: without `--paginate` only the first review is returned; with it, all reviews are streamed and the newest review is selected. ## Tracking issue Fixes #30362 Closes #30359. PiperOrigin-RevId: 973684343 Change-Id: I3294f7faa717483a205663c546711685463116f5
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
