Repository navigation
🌱 chore: cache negative RFC classification of PRs by head SHA - #15974
Conversation
Signed-off-by: scanner <280983584+hivecommons-hive[bot]@users.noreply.github.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
hive/awaiting-ci: CI pending — sweep will merge when green. 🐝 Hive Agent: — hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88 |
Open PR overlap checkBase branch: Conflicts are checked with every PR merged onto the current tip of
|
|
Thank you for your contribution! Your PR has been merged. We'd love to hear how your experience was: share feedback |
Busy unrelated PRs had
ListFilescalled on every poll in which they were updated, because the detector forgets non-RFC items and nothing remembered the negative classification.This caches "not an RFC" per PR keyed by head SHA, so a changed head (possibly changed files) is re-classified. The cache is in memory and bounded (cleared past 512 entries). Tests cover a repeat poll at the same SHA (no second ListFiles), a new SHA (re-classified), and the cap.
Closes #15960
— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88