feat(tcfeed): keep repositories nobody has starred out of the table - #133
Merged
Conversation
Nine of the seventeen repositories asked in today's batch had under fifteen stars and five had two or fewer. In several the request arrived as issue #1 and pull request #1 of a repository nobody has looked at yet — coldmill, EntityIdentifierResolver, gomorph, svarm, claude-bridge. Two reasons to stop, and the second is the one that matters: They will not be read. A repository with no stars and no issues has no maintainer attention to win. The whole premise of asking first is that somebody is there to answer. It is the shape of activity the acceptable use policy is least forgiving about. Bulk unsolicited pull requests are judged on the pattern, not on each one, and "opened issue #1 in forty repositories with no stars" is that pattern described exactly. TCFEED_MIN_STARS, default 5, 0 turns it off. Five rather than fifteen because the aim is to drop repositories that are unattended, not small ones — nsproxy at 84 stars and ZeroDroid at 6 are real projects with real users, and the floor should not have an opinion about them. Placed above the scan, so a repository under the floor is never cloned. It costs one metadata call and saves a clone. Remembered rather than reconsidered, which is the one real trade here: a star count can change where `archived` cannot, so a repository that grows past the floor later will not come back. Re-deciding it every run would instead burn one of the twenty slots each time and crowd out candidates that would actually be scanned. Verified both directions against an isolated cache: at 999999 every repository is gated and nothing is cloned, and the table comes back empty; at 0 no repository is gated and the table builds as before. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ThreatCrush Security Scan67 finding(s) HIGH/CRITICAL: 11 | MEDIUM: 55 | LOW: 1
…and 17 more. Full results in the Security tab. Snippets are redacted; ThreatCrush never prints matched credential material. |
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.
Nine of the seventeen repositories asked in today's batch had under fifteen stars and five had two or fewer. In several, the request arrived as issue #1 and pull request #1 of a repository nobody has looked at yet —
coldmill,EntityIdentifierResolver,gomorph,svarm,claude-bridge.Two reasons to stop, and the second is the one that matters:
What changed
TCFEED_MIN_STARS, default 5,0turns it off.Five rather than fifteen because the aim is to drop repositories that are unattended, not small — nsproxy at 84 stars and ZeroDroid at 6 are real projects with real users, and the floor should not have an opinion about them.
Placed above the scan, so a repository under the floor is never cloned. It costs one metadata call and saves a clone.
The one real trade
It is remembered rather than reconsidered. A star count can change where
archivedcannot, so a repository that grows past the floor later will not come back. Re-deciding it every run would instead burn one of the twenty slots each time and crowd out candidates that would actually be scanned. Flagging it explicitly rather than burying it.Verification
Both directions, against an isolated
TCFEED_CACHEso real state was untouched:TCFEED_MIN_STARS=999999— every repository gated, nothing cloned, table comes back empty:TCFEED_MIN_STARS=0— no repository gated, table builds as before (Vulkan-Docs 3317, hexclave 6842).🤖 Generated with Claude Code