Repository navigation
fix(identity): exclude broken repos from stuck leaderboard alarm - #202
Merged
Merged
Conversation
harlan-github-agent
Bot
added
harlan-agent-running
Contributor
Author
🤖 MERGED
GitHub merged this pull request. No material findings were recorded. The pull request closed. |
harlan-github-agent
Bot
added
harlan-agent-blocked
harlan-github-agent
Bot
added
harlan-agent-running
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🔗 Linked issue
Closes #200
❓ Type of change
📚 Description
The nightly check-in flagged
iamzhihuix/happy-claude-skillsas a stuck leaderboard approval every night. The repo was deleted upstream on 2026-09-04 (404 verified), so itsreposrow carriesbroken_sinceand no healthy skill row can ever exist again. The stuck query read that permanent absence as "review never became visible", refiring the alarm and driving both archived reports AMBER.A review on a repo whose
reposrow is already broken describes a known state: the breakage is reported by the broken-repo metrics. The stuck query now skips reviews whose repo is marked broken. Reviews with noreposrow at all still alarm, since those are the ones genuinely waiting on the pipeline.I did not backfill or silence the historical AMBER reports; the next nightly run goes quiet on its own.