Repository navigation
Pin sha separate workflows - #38036
Merged
Merged
Conversation
Split the OPS status into two workflows. One generates the report, the second updates the PR description. The second runs in a different context and is the only workflows with write perms.
Pin the commit SHA for each workflow.
BillWagner
requested review from
gewarren
and
a balanced review from Copilot
and removed request for
Copilot
October 28, 2026 17:00
Copilot stopped reviewing on behalf of
BillWagner due to an error
October 28, 2026 17:02
gewarren
approved these changes
Oct 28, 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.
This makes two related changes:
First, use the updated OPS preview workflow implemented in dotnet/docs-actions#37. This separates the status creation from the work that updates the PR descriptions. The security boundary between them means the first runs in the PR author's context, with minimal rights. The second is only triggered when the work completes and always runs in the base branch context to update the PR and description.
Second, pin all actions to the commit SHA.