Repository navigation
Conversation
EXCLUDE_REPOS was only applied when aggregating, so excluded repos were still queried for views and contributor stats. For huge repos (e.g. libsdl-org/SDL) that endpoint returns 504s or truncated responses that fail the whole run.
ArnauNau
force-pushed
the
skip-excluded-repos-early
branch
from
October 18, 2026 15:55
a585ec6 to
ad20b2e
Compare
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.
EXCLUDE_REPOSis only applied when aggregating inmain.zig, so excluded repositories are still queried for/traffic/viewsand/stats/contributors, and, when that endpoint keeps returning 202, cloned locally to count lines changed.Large upstream projects are the most likely repos to exclude, and also where those requests are the most expensive and fragile. In my case
libsdl-org/SDLreturned 504 from/stats/contributors, which failed the whole run (any status other than 202/403/429 is fatal) even though the repo was excluded.This passes the exclude patterns into
Statistics.initand skips matching repos right after the GraphQL contributions query, before any per-repo REST requests. Skipped repos are marked as seen, so later date ranges skip them too.Notes:
glob.matchAny, and the aggregation-time filter inmain.zigstays, so it still applies to--json-input-file.--json-output-file.Testing:
zig build,zig build testandzig fmt --check src/pass. In my own copy of the workflow, runs that failed on the SDL 504 now succeed, and the language percentages match a separate computation from the same GraphQL data.