Skip to content

ci(cspell-misc): declare contents: read#8163

Open
arpitjain099 wants to merge 1 commit into
Azure:mainfrom
arpitjain099:ci/add-permissions
Open

ci(cspell-misc): declare contents: read#8163
arpitjain099 wants to merge 1 commit into
Azure:mainfrom
arpitjain099:ci/add-permissions

Conversation

@arpitjain099
Copy link
Copy Markdown

Small follow-up to align cspell-misc.yml with its sibling cspell-ext.yml, which already declares permissions: contents: read at the top level. The workflow only checks out the tree and runs cspell lint - no GitHub API surface - so the same scope fits.

Confirmed with yaml.safe_load parse. No behavior change.

The sibling cspell-ext.yml already uses permissions: contents: read.
cspell-misc only checks out and runs cspell - same scope is correct.
Copilot AI review requested due to automatic review settings May 13, 2026 09:45
@microsoft-github-policy-service microsoft-github-policy-service Bot added the customer-reported identify a customer issue label May 13, 2026
@microsoft-github-policy-service
Copy link
Copy Markdown
Contributor

Thank you for your contribution @arpitjain099! We will review the pull request and get back to you soon.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Aligns the cspell-misc GitHub Actions workflow with the existing cspell-ext workflow by explicitly declaring minimal GITHUB_TOKEN permissions (contents: read). This supports the repo’s least-privilege CI posture while keeping behavior unchanged for a workflow that only checks out code and runs cspell lint.

Changes:

  • Add top-level permissions: contents: read to .github/workflows/cspell-misc.yml to match .github/workflows/cspell-ext.yml.
  • No change to job steps or triggers; only the workflow token scope is constrained.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

customer-reported identify a customer issue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants