Repository navigation
feat: link the upstream issue/PR for actions with no node24 release; flag archived repos - #3
Conversation
…flag archived repos
|
Blackman99
left a comment
There was a problem hiding this comment.
Reviewed against GOAL.md: on goal. For actions with no node24 release, actnode can now say where the upstream fix is being tracked, and it flags archived repos that will never get one.
- Lookups are bounded to one search per repo per run and disk-cached. Failures and rate limits return None without caching the miss, so a flaky network never blocks a scan.
--no-upstreamgives an offline/deterministic path._pick_issuematchesnode24,node 24,node.js 24andnodejs-24in titles, preferring open, then most-discussed.
Small note for later: the archived check costs one extra API call per no-fix action. That's fine at this volume, but worth caching to disk alongside the issue lookup if anyone hits rate limits. Will merge once CI is green.
Roadmap item: track upstream "no node24 release yet" actions.
no-fixfindings now search the action's repo once for an issue/PR whose title mentions node24 (open first, then most discussed) and link it in text, Markdown and JSON (upstream_issue).--no-upstreamskips the lookups; results are disk-cached with the tags; rate-limited searches are skipped silently.