Repository navigation
docs: document tokenless OIDC for public repositories and use covdbg 1.5.1 - #5
Merged
Merged
Conversation
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.
What this changes
1.5.1, the current release.id-token: writeand covdbg proves the repository with the job's GitHub OIDC token. It also covers skipping fork pull requests (they get no OIDC token) and warns againstpull_request_target.COVDBG_PROJECT_TOKENstays documented for private repositories.Why
The README still said that public repositories need a project token, which stopped being true with covdbg 1.5.0. The wording follows covdbg.com/docs/integrations/github-actions.
How it was verified
Docs only.
liasoft/covdbg-quick-startruns green with this setup and no secret.