Repository navigation
Discovery: flag suspicious stars only when forks and commits are hollow too; review after 30 days - #10108
Merged
Conversation
…ow too; review after 30 days The velocity rule (15 stars a day, at least 300) flagged 73 open PRs, 61 of them genuine projects that the press writes about. A flag now also needs fewer than 10 forks or more than 30 stars per fork, and fewer than 300 commits. The reason gets its own label, suspicious-stars, next to manual-check-needed, and the PR body carries the numbers either way. review-suspicious-stars.yml (monthly) re-reads the numbers of labeled PRs older than 30 days and removes both labels with one comment when forks or commits have caught up. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DZvaN9tm5taf5avUvVtmyq
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.
Items 1, 3 (for the discovery bot) and 6 of the lessons from yesterday's review of the 107
manual-check-neededPRs.The rule. The velocity rule alone (15 stars a day since creation, at least 300, under two years old) had flagged 73 open PRs; 61 were genuine projects that the press writes about (the storytold apps among them). A flag now also needs the repository to look hollow: fewer than 10 forks or more than 30 stars per fork, and fewer than 300 commits. The commit count costs one request (the last page number of
commits?per_page=1). A fast-growing but established repository gets the numbers as a neutral note in the PR body instead of a label.The reason on the PR. A flagged PR gets
suspicious-stars(the reason) next tomanual-check-needed(what auto-merge, the health report and the stale ladder look at, unchanged), and the body carries stars, forks, commits and age. 17 of the 107 PRs had no visible reason for their label, and a bot label and a hand-applied one could not be told apart because the bot works with the maintainer's token.The follow-up.
.github/workflows/review-suspicious-stars.yml(monthly;workflow_dispatchwithdays,limit,dry_rundefault true) runscode/review-suspicious-stars.sh: for labeled PRs older than 30 days it reads stars, forks and commits again and, when they have caught up, removes both labels with one comment carrying the numbers (marker<!-- appimagehub-stars-review -->). A repository that still looks hollow keeps its labels; the comment is never repeated. Requests go through a countingapi()with a quota reserve, as in #10014.AGENTS.md section 6 describes both.
bash -n, shellcheck and actionlint pass; the discovery change is not testable from this sandbox (no API access to other repositories).🤖 Generated with Claude Code
https://claude.ai/code/session_01DZvaN9tm5taf5avUvVtmyq
Generated by Claude Code