Potential fix for code scanning alert no. 2: Workflow does not contain permissions #101
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.
Potential fix for https://github.com/conekta/openapi/security/code-scanning/2
In general, to fix this issue you explicitly declare minimal
GITHUB_TOKENpermissions either at the workflow root or for the specific job. This overrides any potentially over‑permissive repository/organization defaults and adheres to the principle of least privilege.For this specific workflow, the safest and simplest fix without changing existing functionality is to add a
permissions:block granting only read access to repository contents. Therdme-openapijob only checks out the repository (actions/checkout@v3) and then callsreadmeio/rdme@v8with an API key secret; it does not create releases, modify issues, or push commits, socontents: readis sufficient. We will addpermissions: contents: readunder therdme-openapijob definition, aligned withruns-on:. This change is in.github/workflows/rdme-openapi.yml, near line 17.No additional imports or methods are needed; this is purely a YAML configuration change.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.