Repository navigation
ci(clone-tracking): use TRAFFIC_TOKEN for the traffic API; skip with a warning when unset - #2532
Merged
Merged
Conversation
…rning when unset
/repos/{repo}/traffic/{clones,views} need the "Administration: read"
repository permission, which GITHUB_TOKEN cannot be granted, so every
scheduled run since 2026-08-15 failed with HTTP 403. Use a dedicated
TRAFFIC_TOKEN secret (fine-grained PAT, RuView only, Administration: read)
and, while it is unset, emit a ::warning:: and skip the scrape instead of
failing the job.
Co-Authored-By: claude-flow <ruv@ruv.net>
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
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.
Problem
GitHub Clone Tracking → data/clone-data.rvfhas failed on every scheduled run since 2026-08-15. The latest was run 41260973562 on 2026-11-01:The traffic endpoints need the Administration: read repository permission. The workflow
GITHUB_TOKENcan never be granted that permission, whatever thepermissions:block says, so no change to the YAML alone can fix this.Fix
TRAFFIC_TOKENsecret: a fine-grained PAT scoped to ruvnet/RuView with Administration: read only.::warning::and skips the scrape, so nothing is recorded silently.GITHUB_TOKEN(contents: write).Owner action
Add the repository secret
TRAFFIC_TOKEN: a fine-grained PAT for ruvnet/RuView with Administration: read. There is no GCP Secret Manager mapping for it.Then run the workflow once with
workflow_dispatchto backfill. GitHub keeps only 14 days of traffic data, so anything older than that is already lost.🤖 Generated with claude-flow