ci: wire the Codacy coverage upload so it self-activates - #59
Merged
Conversation
The step was commented out with instructions, which meant enabling it needed a second PR that someone has to remember. It is live now and guarded by `if: env.CODACY_PROJECT_TOKEN != ''`, so with no secret it simply skips and the job stays green — and it starts uploading by itself the moment the secret is added. The secret has to be job-level env for the step's `if` to see it. The comment now names WHICH token: a repository token (Codacy → the repo → Settings → Integrations), not an account one. An account token carries the whole Codacy user's permissions across every repo; the repository token is scoped to this one, so a leak cannot reach anything else. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Up to standards ✅🟢 Issues
|
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.
The upload step was commented out with instructions — which means enabling it needs a second PR someone has to remember.
It's live now, guarded by
if: env.CODACY_PROJECT_TOKEN != '':(The secret has to be job-level
envfor a step'sifto see it.)The comment also now names which token, because the two are easy to confuse: a repository token, not an account one. An account token carries your whole Codacy user's permissions across every repo; the repository token is scoped to this one, so a leak can't reach anything else.
🤖 Generated with Claude Code