Skip to content

Harden pr-description-checker workflow - #9049

Open
Damyan Pepper (damyanp) wants to merge 1 commit into
microsoft:mainfrom
damyanp:damyanp-workflow-trigger-mitigation
Open

Damyan Pepper (damyanp) wants to merge 1 commit into
microsoft:mainfrom
damyanp:damyanp-workflow-trigger-mitigation

Conversation

@damyanp

@damyanp Damyan Pepper (damyanp) commented Oct 19, 2026 •

Copy link
Copy Markdown
Member

Harden the pr-description-checker workflow.

Assisted by GitHub Copilot.

Set explicit contents: read / pull-requests: write permissions, check out only the trusted base-repo .github directory, and do not persist credentials. Update actions/checkout to the v5.1.0 pin already used in this repo.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 480e2f3f-26d5-4ab8-86e9-9bd488a7e2a3

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟢 Approval recommended

The focused hardening preserves required access, with no identified blocking issues.

No open issues 🎉

What changed in this PR

Hardens the PR description checker workflow by reducing checkout scope and credential exposure.

Changes:

  • Sets explicit repository-read and pull-request-write permissions.
  • Upgrades the pinned checkout action to v5.1.0.
  • Restricts checkout to .github and disables credential persistence.
File Description
.github/​workflows/​pr-description-checker.yml Tightens permissions and checkout configuration for the description checker.

Review effort: Balanced

@damyanp Damyan Pepper (damyanp) changed the title Harden PR description checker pull_request_target workflow Harden pr-description-checker workflow Oct 19, 2026

This branch has not been deployed

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

Labels

None yet

Projects

Status: New

Development

Successfully merging this pull request may close these issues.

2 participants