Auto-approve generated docs sync PRs - #3411
Merged
Merged
Conversation
rosslovas
marked this pull request as ready for review
August 21, 2026 02:12
borland
approved these changes
Aug 21, 2026
borland
left a comment
borland
left a comment
Contributor
There was a problem hiding this comment.
The checks in the if statement are many, and specific. This looks pretty lock-tight to me. Approved
|
Pull request environment is available at https://stoctodocspr3411.z22.web.core.windows.net. You can view the ephemeral environment status in Octopus Deploy. This environment will be automatically deprovisioned when the pull request is closed, or after 7 days of inactivity. |
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
3 participants
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.
Summary
We want automatically generated PRs like #3410 to merge automatically so long as the build passes. For this they need to be approved, so this PR will automatically approve them as the github-actions bot (which, importantly, is a different user to the author of the PR and thus satisfies the review required check).
Risk
Automatically approving naturally always carries a risk of incorrectly approving a malicious PR; please sanity check that the workflow contains no holes in this regard!