Take note :
this feature automatically adds the skara command
/reviewers 2
to all reviews with the "client" label
The requirement is therefore
- at least one Capital R "Reviewer" - as per the census
- at least one other approval.
This enforces the requirement we've always had in client.
Also note that
- skara bots have applied it to all current open reviews
- it means the ready label has been removed from some reviews with only
one approval since the last commit
- since it is 'touching' all the open PRs, this has also triggered the
AI template, so any PRs missing it are no longer 'rfr', regardless of
the number of approvals.
- if it has the AI template checked, and had 2 reviewers since the last
commit, with at least one of those being a Reviewer, it should still be
ready.
-phil.
-------- Forwarded Message --------
Subject: New Skara Feature – Label-driven Reviewer Requirements
Date: Thu, 16 Apr 2026 18:31:54 +0000
From: Zhao Song <[email protected]>
To: [email protected] <[email protected]>
Confidential - Oracle Restricted \Including External Recipients
Hi all,
I'd like to announce a new Skara feature that introduces label-driven
reviewer requirements for pull requests in the JDK repository.
With this change, if a pull request is associated with certain labels,
the Skara bot will automatically default to two reviewers. This
requirement does not apply to Backport or Merge-style pull requests.
This behavior can still be overridden using the `/reviewers` command.
Initially this will apply to pull requests labeled with: hotspot,
hotspot-gc, hotspot-compiler, hotspot-runtime, and client.
Relevant issues:
https://bugs.openjdk.org/browse/SKARA-2573
https://bugs.openjdk.org/browse/SKARA-2708
Thanks,
Zhao
Confidential - Oracle Restricted \Including External Recipients
