Skip to content

ci(test-docs-builder-setup): cap GITHUB_TOKEN to contents: read#169

Closed
arpitjain099 wants to merge 3 commits into
elastic:mainfrom
arpitjain099:chore/declare-workflow-perms
Closed

ci(test-docs-builder-setup): cap GITHUB_TOKEN to contents: read#169
arpitjain099 wants to merge 3 commits into
elastic:mainfrom
arpitjain099:chore/declare-workflow-perms

Conversation

@arpitjain099

Copy link
Copy Markdown
Contributor

The test-docs-builder-setup workflow tests the docs-builder setup. No GitHub API writes, so workflow-level contents: read is the right cap.

Post-CVE-2025-30066 (tj-actions/changed-files) hardening pattern. YAML validated locally.

@arpitjain099 arpitjain099 requested a review from a team as a code owner May 25, 2026 22:51
@arpitjain099 arpitjain099 requested a review from Mpdreamz May 25, 2026 22:51
@github-actions

Copy link
Copy Markdown

Label error. Requires exactly 1 of: automation, breaking, bug, changelog:skip, chore, ci, dependencies, documentation, enhancement, feature, fix. Found:

@arpitjain099

Copy link
Copy Markdown
Contributor Author

Consolidating to avoid a duplicate: #157 already declares the same read-only permissions on these workflow(s) (and others), so I'm closing this one in its favor. Apologies for the overlap.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant