Skip to content

[docs] Self-healing documentation fixes from issue analysis - 2026-03-11#20569

Merged
pelikhan merged 1 commit intomainfrom
doc-healer/guard-policy-safeoutputs-derivation-2026-03-11-2d32b2011a01a289
Mar 11, 2026
Merged

[docs] Self-healing documentation fixes from issue analysis - 2026-03-11#20569
pelikhan merged 1 commit intomainfrom
doc-healer/guard-policy-safeoutputs-derivation-2026-03-11-2d32b2011a01a289

Conversation

@github-actions
Copy link
Contributor

Self-Healing Documentation Fixes

This PR was automatically created by the Daily Documentation Healer workflow.

Gaps Fixed

Root Cause

DDUw ran at ~04:50 UTC on 2026-03-11 and produced PR #20468 (documenting safe-outputs.environment). PR #20467 was merged at 18:21 UTC — over 13 hours after DDUw completed. This is the same late-merge blind-spot pattern documented in the previous two healer runs (#20254, #20412): features merged in the afternoon UTC window fall entirely outside DDUw's single early-morning scan.

DDUw Improvement Suggestions

  1. Run DDUw twice daily (e.g. 06:00 UTC and 20:00 UTC) to reduce the blind spot from ~20 hours to ~10 hours. This is the third consecutive healer run identifying a late-UTC-day merge as the root cause.
  2. Expand DDUw's scan window to 36 hours with deduplication. A wider window would reliably catch features merged late in the prior day regardless of schedule.

Analyzed Issues (last 7 days, label: documentation, state: closed)

Issue Title DDUw addressed? Action
#20370 [cli-consistency] CLI Consistency Issues - Help Flag Descriptions Addressed by PR #20375 (CLI fix) No action
#20248 Improve actionability of failure issues Addressed by PR #20266 No action
#20241 Staged mode support needs better docs Addressed by PR #20269 (staged-mode.md) No action
#20218 [cli-consistency] CLI Consistency Issues and Missing Flags Addressed by PR #20272 No action
#19866 [cli-consistency] CLI Consistency Issues - 2026-03-06 CLI binary help text, not docs/ No action
#19836 [research] Overview of docs improver agents Research question, not a docs gap No action
#19815 [ubuntu-image] research: update Ubuntu runner image analysis research/ file, not docs/ No action
#19727 [cli-consistency] CLI Consistency Issues - 2026-03-05 CLI binary help text No action
#19603 [workflow-style] Normalize report formatting Workflow instruction file No action
#19601 [cli-consistency] CLI Consistency Issues - 2026-03-04 CLI binary help text No action
#19222 [cli-consistency] CLI Consistency Issues - 2026-03-02 CLI binary help text No action

The guard-policy auto-derivation gap was discovered by cross-referencing commits merged after DDUw's last run, not from a closed issue.

Files Changed

  • docs/src/content/docs/reference/github-tools.md — added "Safe Outputs Integration" subsection to the Guard Policies section documenting automatic safeoutputs guard-policy derivation

Related

Generated by Daily Documentation Healer ·

  • expires on Mar 14, 2026, 12:00 AM UTC

Generated by Daily Documentation Healer ·

  • expires on Mar 14, 2026, 7:30 PM UTC

…ation

When a GitHub MCP guard-policy is configured with a specific repos array,
the compiler (since #20467, gateway v0.1.14) automatically derives a linked
write-sink guard-policy for the safeoutputs MCP server. Document this
behavior in the Guard Policies section of github-tools.md.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions github-actions bot added automation documentation Improvements or additions to documentation labels Mar 11, 2026
@pelikhan pelikhan marked this pull request as ready for review March 11, 2026 19:32
Copilot AI review requested due to automatic review settings March 11, 2026 19:33
@pelikhan pelikhan merged commit fc274b1 into main Mar 11, 2026
@pelikhan pelikhan deleted the doc-healer/guard-policy-safeoutputs-derivation-2026-03-11-2d32b2011a01a289 branch March 11, 2026 19:33
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds documentation for the recently introduced compiler behavior that auto-derives a safeoutputs MCP guard-policy from GitHub Tools guard-policy configuration.

Changes:

  • Added a new “Safe Outputs Integration” subsection under GitHub Tools → Guard Policies.
  • Documented how tools.github.repos guard-policy settings influence safeoutputs MCP configuration.
Comments suppressed due to low confidence (1)

docs/src/content/docs/reference/github-tools.md:164

  • The inline comment # safe outputs can write to the guard-policy repos is misleading: the derived safeoutputs guard-policy is a gateway/MCP write-sink policy (accept list), not a GitHub write authorization mechanism for safe output jobs. Consider rewording to reflect that the safeoutputs MCP server is permitted to accept private data for the specified repos/patterns (via private:<pattern>), rather than implying it controls where safe outputs can write.
safe-outputs:
  create-issue:                # safe outputs can write to the guard-policy repos
</details>



---

💡 <a href="/github/gh-aw/new/main?filename=.github/instructions/*.instructions.md" class="Link--inTextBlock" target="_blank" rel="noopener noreferrer">Add Copilot custom instructions</a> for smarter, more guided reviews. <a href="https://docs.github.com/en/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot" class="Link--inTextBlock" target="_blank" rel="noopener noreferrer">Learn how to get started</a>.<br><br>You can also share your feedback on Copilot code review. [Take the survey](https://www.surveymonkey.com/r/XP6L3XJ).

Comment on lines +149 to +151
When you configure `repos` as an array of specific repository patterns, the compiler automatically derives a linked guard-policy for the [safe outputs](/gh-aw/reference/safe-outputs/) MCP server. Each entry in the `repos` list is added as a `private` accept entry in the safeoutputs policy, allowing the MCP gateway to read private repository data through the GitHub tools and still write outputs via safeoutputs.

This derivation happens at compile time and requires no additional configuration. If you use `repos: "all"` or `repos: "public"`, no safeoutputs guard-policy is derived.
Copy link

Copilot AI Mar 11, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Safe Outputs guard-policy derivation described here doesn’t match the compiler behavior. In deriveSafeOutputsGuardPolicyFromGitHub (pkg/workflow/mcp_github_config.go), every GitHub repos value that enables guard-policies results in a safeoutputs write-sink.accept entry prefixed with private: (e.g., private:myorg/private-repo), and repos: "all" / repos: "public" map to accept: ["private:*"] rather than producing no derived policy. Please update this section to describe the private:<pattern>/private:* behavior accurately.

This issue also appears on line 162 of the same file.

Copilot uses AI. Check for mistakes.
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.

2 participants