Skip to content

[docs] Update documentation for features from 2026-05-23#34202

Merged
pelikhan merged 1 commit into
mainfrom
docs/protected-files-request-review-2026-05-23-ab7892d4b2e61096
May 23, 2026
Merged

[docs] Update documentation for features from 2026-05-23#34202
pelikhan merged 1 commit into
mainfrom
docs/protected-files-request-review-2026-05-23-ab7892d4b2e61096

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

Documentation Updates - 2026-05-23

This PR updates the documentation based on features merged in the last 24 hours.

Features Documented

📝 Detailed Changes & References

Changes Made

  • docs/src/content/docs/reference/safe-outputs-pull-requests.md
    • Policy Options table for protected-files now lists request_review as the default; previous rows kept for blocked, fallback-to-issue, allowed.
    • Object-form example comment updated: default: blockeddefault: request_review.
    • workflow_call example description updated to enumerate all four valid policy values.
  • docs/src/content/docs/reference/threat-detection.md
    • Policy Options table mirrors the new request_review default and added value.
    • New "When Detection Returns a Warning" paragraph under Error Handling describing the REQUEST_CHANGES review the handler now submits on warning detections, including composition with the protected-files review when both fire.

Verified against current source:

  • Default policy: compiler_safe_outputs_handlers.go sets protectedFilesPolicy := "request_review" and the spec test compiler_safe_outputs_config_test.go asserts the same default.
  • Threat-warning review path: actions/setup/js/create_pull_request.cjs builds requestChangesSections from detectionCaution + protected-files signals and submits a single REQUEST_CHANGES review (falling back to COMMENT on "own PR" errors).

Merged PRs Referenced

Other merged PRs scanned (no docs update required)

Skipped Issues

Notes

No other unaddressed open documentation-labeled issues represent a confirmed gap that this run could close.

Generated by 📝 Daily Documentation Updater · ● 18.5M ·

  • expires on May 24, 2026, 11:09 AM UTC

…-warning REQUEST_CHANGES review

The `protected-files` policy on `create-pull-request` and
`push-to-pull-request-branch` now defaults to `request_review`
(creates the PR and submits a REQUEST_CHANGES review) and accepts a
fourth value of that same name. The reference tables previously listed
only `blocked`/`allowed`/`fallback-to-issue` and marked `blocked` as the
default, which no longer matches runtime behavior.

PR #34133 additionally extended `create_pull_request` to submit a
REQUEST_CHANGES review when threat detection returns a warning (with the
detection reason and run-log link), composing with the protected-files
review when both fire. Added a short "When Detection Returns a Warning"
note under Error Handling.

Refs: #34133

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@github-actions github-actions Bot added automation documentation Improvements or additions to documentation labels May 23, 2026
@pelikhan pelikhan merged commit 6fe343f into main May 23, 2026
@pelikhan pelikhan deleted the docs/protected-files-request-review-2026-05-23-ab7892d4b2e61096 branch May 23, 2026 12:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automation documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant