Add octo-sts trust policy for validation PR comments#23269
Merged
Conversation
lucia-sb
approved these changes
Apr 10, 2026
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
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.
What does this PR do?
Adds an octo-sts trust policy (
self.validate.pull-request.sts.yaml) that grants the validation workflow permission to post PR comments with validation results.This policy is a prerequisite for #23249, which replaces the 25 sequential validation steps with a parallel
ddev validate allcommand that posts structured failure reports as PR comments.Motivation
The validation workflow needs
pull_requests: writeto post comments on PRs. The octo-sts action exchanges an OIDC token for a scoped GitHub token using this trust policy, which is more secure than usingsecrets.GITHUB_TOKENwith broad permissions.Review checklist (to be filled by reviewers)
qa/skip-qalabel if the PR doesn't need to be tested during QA.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged