[docs] Update documentation for features from 2026-03-08

[github-actions]

Documentation Updates - 2026-03-08

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

Features Documented

• resources: frontmatter field — declares additional files to fetch with gh aw add (from feat(add): fetch dispatch-workflow dependencies and resources when adding remote workflows #19965)
• Automatic dispatch-workflow dependency fetching during gh aw add (from feat(add): fetch dispatch-workflow dependencies and resources when adding remote workflows #19965)

Changes Made

• Added ### Resources (\resources:`)section todocs/src/content/docs/reference/frontmatter.md, placed after private:since both fields relate togh aw add` behavior
• Updated docs/src/content/docs/guides/packaging-imports.md to describe what gh aw add automatically fetches (dispatch-workflow deps and resources: files)
• Added a callout to the dispatch-workflow: section in docs/src/content/docs/reference/safe-outputs.md noting that listed workflows are auto-fetched during gh aw add

Merged PRs Referenced

• feat(add): fetch dispatch-workflow dependencies and resources when adding remote workflows #19965 — feat(add): fetch dispatch-workflow dependencies and resources when adding remote workflows

Notes

Other merged PRs from this period were already documented as part of their own PRs:

• Add protected-files support to runtimes and enforce protected file protection in safe outputs #19958 (protected-files) — docs updated in the PR itself
• Enforce strict: true for public repositories in lockdown validation #19948 (strict mode enforcement) — docs updated in the PR itself
• feat: Add push_repo_memory MCP tool for early size validation #19977 (push_repo_memory) — internal system improvement, no user-facing docs needed
• Improve compile command help text to clarify input/output formats #19988 (compile help text) — minor CLI text change, no docs update needed

Generated by Daily Documentation Updater · ◷

• expires on Mar 9, 2026, 4:24 AM UTC

[Copilot]

Pull request overview

Updates the documentation to cover new gh aw add behavior introduced in #19965: fetching dispatch-workflow dependencies and additional files declared via a new resources: frontmatter field.

Changes:

• Documented the new resources: frontmatter field in the frontmatter reference.
• Updated the packaging/imports guide to explain what gh aw add auto-fetches during installation.
• Added a note to the dispatch-workflow: safe output reference about dependency fetching during gh aw add.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
docs/src/content/docs/reference/frontmatter.md	Adds reference docs for resources: and how it relates to gh aw add.
docs/src/content/docs/guides/packaging-imports.md	Clarifies that gh aw add fetches dispatch-workflow deps and resources: files.
docs/src/content/docs/reference/safe-outputs.md	Adds a callout note about dispatch-workflow auto-fetch behavior during installs.

Comments suppressed due to low confidence (1)

docs/src/content/docs/reference/frontmatter.md:91

• “Placed alongside the main workflow” is ambiguous/inaccurate for nested resource paths: resources are written under the target workflows directory preserving their relative path (e.g. shared/helper-action.yml becomes .github/workflows/shared/helper-action.yml), not necessarily in the same folder as the main workflow file. Consider clarifying the destination path behavior.

When a user runs `gh aw add` to install this workflow, each listed file is also downloaded and placed alongside the main workflow in the target repository. This ensures companion workflows and custom actions the main workflow depends on are available after installation.

---

💡 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.

[Copilot]

The text implies resources: is only for companion files "stored in the same directory", but the implementation resolves each entry relative to the workflow’s directory and allows subpaths (e.g. shared/helper-action.yml) as well as repo-root paths (leading /). Consider rephrasing to avoid suggesting resources must be co-located in the same folder.

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

[Copilot]

This note reads as if gh aw add always fetches dispatch-workflow dependencies, but the current behavior only fetches them when adding a workflow from a remote repository; local-path adds don’t download additional workflows. Consider wording like “When adding a workflow from a remote repo with gh aw add…” to avoid misleading users.

Suggested change

	> When installing a workflow with `gh aw add`, workflows listed in `dispatch-workflow` are automatically fetched and added to the target repository alongside the main workflow.
	> When adding a workflow from a remote repo with `gh aw add`, workflows listed in `dispatch-workflow` are automatically fetched and added to the target repository alongside the main workflow.