Potential fix for code scanning alert no. 1: Workflow does not contain permissions #205
+3
−0
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/ultralytics/docs/security/code-scanning/1
To fix the issue, we need to add a
permissions
block to the workflow. Since the workflow does not require write access to repository contents or other resources, we can set the permissions tocontents: read
, which is the minimal privilege required for most workflows. This block can be added at the root level of the workflow to apply to all jobs, or it can be added to individual jobs if different permissions are needed for each.In this case, adding the
permissions
block at the root level is the best approach, as it simplifies the configuration and ensures consistent permissions across all jobs.Suggested fixes powered by Copilot Autofix. Review carefully before merging.
🛠️ PR Summary
Made with ❤️ by Ultralytics Actions
🌟 Summary
Improved security for the domain-checking workflow in the Ultralytics docs repository. 🔒
📊 Key Changes
🎯 Purpose & Impact