Potential fix for code scanning alert no. 2: Workflow does not contain permissions#1891
Merged
rkaraivanov merged 2 commits intomasterfrom Oct 14, 2025
Merged
Potential fix for code scanning alert no. 2: Workflow does not contain permissions#1891rkaraivanov merged 2 commits intomasterfrom
rkaraivanov merged 2 commits intomasterfrom
Conversation
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
rkaraivanov
approved these changes
Oct 14, 2025
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
2 participants
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/IgniteUI/igniteui-webcomponents/security/code-scanning/2
To resolve this issue, add a
permissionsblock to the workflow. It should be added at the top level (root) of the workflow file, so it applies to all jobs by default. For typical npm publish workflows, onlycontents: readis needed because publishing to npm uses an external token inNODE_AUTH_TOKEN, and no GitHub APIs that require write access are being called. To implement this, insert the following at the top (after thename:line but beforeon:):No other changes, imports, or method definitions are required.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.