Skip to content

[docs] Self-healing documentation fixes from issue analysis - 2026-02-28#18898

Merged
pelikhan merged 2 commits intomainfrom
doc-healer/2026-02-28-guard-policies-57ee6c042bd8846a
Feb 28, 2026
Merged

[docs] Self-healing documentation fixes from issue analysis - 2026-02-28#18898
pelikhan merged 2 commits intomainfrom
doc-healer/2026-02-28-guard-policies-57ee6c042bd8846a

Conversation

@github-actions
Copy link
Contributor

Self-Healing Documentation Fixes

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

Gaps Fixed

  • Guard policies (repos + min-integrity under tools.github) — The guard policies feature was merged in feat: add guard policies support #18589 (commit 60f482a8, 2026-02-27 21:48 UTC) with no public documentation. Added a new Guard Policies section to docs/src/content/docs/reference/github-tools.md covering:
    • repos field ("all" / "public" / pattern arrays)
    • min-integrity field (none / reader / writer / merged)
    • Validation rules (lowercase, wildcard placement, required-together constraint)
    • Three usage examples

Root Cause

Why DDUw missed this: The guard policies feature was merged on 2026-02-27 at 21:48 UTC — after DDUw's 6 AM UTC daily run. The previous self-healing run (PR #18743, 19:26 UTC on 2026-02-27) also ran before the merge. Today's DDUw (PR #18894) scanned 72 PRs from the last 24 hours but classified the guard policies commit as not requiring documentation — likely because the only clearly user-facing file changed (tools_validation.go) is a validation helper rather than an obvious API surface, and the scratchpad spec doc (scratchpad/guard-policies-specification.md) was not correlated with the need to update public docs.

DDUw Improvement Suggestions

  1. Monitor tools_types.go and tools_parser.go for struct field additions: When GitHubToolConfig (or any *ToolConfig struct) gains new exported YAML-tagged fields, DDUw should flag github-tools.md (or the corresponding tools reference page) as requiring a documentation update. A simple heuristic: if tools_types.go is in the changed files set, scan the diff for new yaml: tags and cross-reference them against the tools reference docs.

  2. Treat scratchpad/*-specification.md additions as documentation signals: When a new spec file is added to scratchpad/, its "Update Documentation" section (if present) is a direct signal to DDUw that public docs need updating. DDUw could scan for the phrase Update Documentation or Update docs in newly added scratchpad files to discover undocumented features.

Related Commits

  • 60f482a8feat: add guard policies support (#18589)

Generated by Daily Documentation Healer

Generated by Daily Documentation Healer

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

Add Guard Policies section to github-tools.md documenting the `repos`
and `min-integrity` frontmatter fields under `tools.github:`, merged
in commit 60f482a (#18589) on 2026-02-27 with no public docs.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions github-actions bot added automation documentation Improvements or additions to documentation labels Feb 28, 2026
@pelikhan pelikhan merged commit 94d39b0 into main Feb 28, 2026
2 checks passed
@pelikhan pelikhan deleted the doc-healer/2026-02-28-guard-policies-57ee6c042bd8846a branch February 28, 2026 19:18
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