Conversation
…mment agent params - Add excluded-files to create-pull-request and push-to-pull-request-branch YAML examples and add explanatory prose in safe-outputs-pull-requests.md - Document pull_request_number and repo agent tool fields for create-pull-request-review-comment in safe-outputs.md, noting that pull_request_number is required when target: "*" is configured
Contributor
There was a problem hiding this comment.
Pull request overview
Documents newly introduced safe-output options/parameters that were previously missing from the reference docs, closing gaps introduced by recent feature merges.
Changes:
- Add
excluded-filestocreate-pull-requestandpush-to-pull-request-branchYAML examples, with an explanation of how exclusions are applied at patch-generation time. - Add documentation for
pull_request_number(required withtarget: "*"), plus optional cross-reporepo, for thecreate_pull_request_review_commenttool.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| docs/src/content/docs/reference/safe-outputs.md | Notes required/optional tool parameters (pull_request_number, repo) for PR review comment creation when targeting arbitrary PRs and/or cross-repo. |
| docs/src/content/docs/reference/safe-outputs-pull-requests.md | Adds excluded-files to relevant safe-output YAML examples and explains exclusion semantics and rationale. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
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.
Self-Healing Documentation Fixes
This PR was automatically created by the Daily Documentation Healer workflow.
Gaps Fixed
excluded-filesfield undocumented forcreate-pull-requestandpush-to-pull-request-branch— Addedexcluded-filesto the YAML examples insafe-outputs-pull-requests.mdfor both safe-output types, plus explanatory prose describing that each pattern is passed as a:(exclude)git magic pathspec at patch generation time, and that excluded files bypassallowed-filesandprotected-fileschecks. PR Addexcluded-filesfield tocreate-pull-requestandpush-to-pull-request-branch#20935 (merged 2026-03-14T18:23Z) introduced this field but touched no docs files.pull_request_numberandrepoagent tool fields undocumented forcreate_pull_request_review_comment— Added a sentence insafe-outputs.mdnoting that whentarget: "*"is configured, the agent must supplypull_request_numberin each tool call (omitting it causes the comment to fail), and thatrepocan be supplied for cross-repository scenarios. PR [safeoutputs] Addpull_request_numberandrepofields tocreate_pull_request_review_commenttool schema #20963 (merged 2026-03-14T18:48Z) added these fields to the tool schema but included no doc update.Root Cause
DDUw ran at ~04:25 UTC on 2026-03-14 and produced PR #20906 (documenting GHES improvements). Both #20935 and #20963 were merged at 18:23Z and 18:48Z respectively — more than 14 hours after DDUw completed. This is the fifth consecutive healer run identifying the same late-UTC-day blind-spot pattern: features merged in the afternoon UTC window fall entirely outside DDUw's single early-morning scan.
DDUw Improvement Suggestions
Analyzed Issues (last 7 days, label: documentation, state: closed)
not_planned— CLI binary help text, notdocs/not_planned— CLI binary help text, notdocs/dependencies:documentation undersells APMnot_planned— CLI binary help text, notdocs/docs/contentThe two documented gaps were discovered by cross-referencing today's commits against DDUw's last scan time, not from a closed issue.
Files Changed
docs/src/content/docs/reference/safe-outputs-pull-requests.md— addedexcluded-filesfield tocreate-pull-requestandpush-to-pull-request-branchYAML examples; added prose explaining the fielddocs/src/content/docs/reference/safe-outputs.md— added note onpull_request_numberandrepoagent tool parameters forcreate-pull-request-review-commentRelated
excluded-filesfield tocreate-pull-requestandpush-to-pull-request-branch#20935 — Addexcluded-filesfield tocreate-pull-requestandpush-to-pull-request-branch(merged 2026-03-14T18:23Z, after DDUw's ~04:25Z run)pull_request_numberandrepofields tocreate_pull_request_review_commenttool schema #20963 — Addpull_request_numberandrepofields tocreate_pull_request_review_commenttool schema (merged 2026-03-14T18:48Z, after DDUw's ~04:25Z run)excluded-filesfield tocreate-pull-requestandpush-to-pull-request-branch#20935 or [safeoutputs] Addpull_request_numberandrepofields tocreate_pull_request_review_commenttool schema #20963 due to timing)References: