[Daily Report] Documentation Quality Report - 2026-06-06

[github-actions]

Summary

I found three documentation-related issues in the tracker. Two are still open markdown-doc gaps, and one already has a current workaround in the docs-site code.

Open doc gaps

• Open issue 20593, "Documentation missing for GH_AW_GITHUB_TOKEN magic secret". The current auth reference at docs/src/content/docs/reference/auth.mdx covers COPILOT_GITHUB_TOKEN, ANTHROPIC_API_KEY, OPENAI_API_KEY, and GEMINI_API_KEY, but it does not explain the GH_AW_GITHUB_TOKEN fallback secret. Related cross-references exist in docs/src/content/docs/reference/glossary.md and docs/src/content/docs/reference/copilot-cloud-agent.mdx, but they are partial and do not replace a dedicated auth section.

• Open issue 27886, "Docs: guidelines for configuring Go module/build cache in a security-conscious way". The current docs only cover the generic cache: frontmatter in docs/src/content/docs/reference/frontmatter.md, the sandbox/runtime notes in docs/src/content/docs/reference/sandbox.md, and the general cache-memory guidance in docs/src/content/docs/reference/cache-memory.md. There is no Go-specific cache recipe or security discussion yet.

Already answered

• Open issue 29545, "Docs problem on android Chrome with large user fonts". The workaround is already present in docs/src/components/CustomHeader.astro and reinforced in docs/src/styles/custom.css. This looks like a docs-site rendering/accessibility fix that is already documented in code comments rather than a missing markdown page.

Recommendation

• Add a dedicated auth note for GH_AW_GITHUB_TOKEN or fold it into the existing auth reference.
• Add a Go cache guide or a Go-specific subsection under cache/sandbox docs.
• Close 29545 with a pointer to the existing header/CSS workaround unless a markdown page is desired for discoverability.

Warning

Firewall blocked 2 domains

The following domains were blocked by the firewall during workflow execution:

• api.github.com
• github.com

💡 Tip: api.github.com is blocked because GitHub API access uses the built-in GitHub tools by default. Instead of adding api.github.com to network.allowed, use tools.github.mode: gh-proxy for direct pre-authenticated GitHub CLI access without requiring network access to api.github.com:

tools:
  github:
    mode: gh-proxy

See GitHub Tools for more information on gh-proxy mode.

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "api.github.com"
    - "github.com"

See Network Configuration for more information.

Generated by 💻 Dev · 48.5 AIC · ◷

• expires on Jun 13, 2026, 9:36 AM UTC