feat(tcfeed): make the budget a backstop, not a pace - #128
Merged
Conversation
30 standing and 20 a day sat right on top of normal use, so every ordinary run hit them. A limit that fires constantly is not consulted, it is routed around: the working habit became TCFEED_PR_STANDING=60 TCFEED_PR_PER_DAY=60 in front of the command, at which point neither number meant anything. 200 and 100. High enough that somebody doing this on purpose never sees them, low enough that a bug cannot empty the whole feed into strangers' repositories overnight. The limit that fires on the thousandth request of a runaway loop is worth more than the one that fires on the twenty-first of a deliberate afternoon. Whether a given afternoon is defensible under GitHub's acceptable use policy is a judgement, and it stays with whoever typed the command. Co-Authored-By: Claude Opus 5 (1M context) <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.
30standing and20/day sat right on top of normal use, so every ordinary run hit them:A limit that fires constantly is not consulted, it is routed around. The working habit had already become
TCFEED_PR_STANDING=60 TCFEED_PR_PER_DAY=60in front of the command — at which point neither number meant anything at all.200 and 100
High enough that somebody doing this on purpose never sees them. Low enough that a bug cannot empty the whole feed into strangers repositories overnight.
The limit that fires on the thousandth request of a runaway loop is worth more than the one that fires on the twenty-first of a deliberate afternoon.
Whether a given afternoon is defensible under GitHubs acceptable use policy is a judgement, and it stays with whoever typed the command. The counters and the
standing:line are unchanged, so the number is still reported on every run — it just no longer refuses.tsc --strict --noEmitclean.🤖 Generated with Claude Code