[docs] Update documentation for features from 2026-03-10#20306
Conversation
There was a problem hiding this comment.
Pull request overview
Updates user-facing documentation to reflect newly merged CLI flags and a new safe-outputs configuration option.
Changes:
- Documents
gh aw new --engine/-eand shows how it injectsengine:into generated frontmatter. - Documents
gh aw run --json/-j,gh aw list --dir/-d, andgh aw audit --repo/-r. - Adds
safe-outputs.report-failure-as-issuedocumentation under global safe-outputs configuration options.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| docs/src/content/docs/setup/cli.md | Adds/extends CLI command examples and option notes for new flags (run --json, audit --repo, new --engine, list --dir). |
| docs/src/content/docs/reference/safe-outputs.md | Documents new global safe-outputs option report-failure-as-issue and its intended behavior. |
💡 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.
| create-issue: | ||
| ``` | ||
|
|
||
| This mirrors the `noop.report-as-issue` pattern. Use this to silence noisy failure reports for workflows where failures are expected or handled externally. |
There was a problem hiding this comment.
This section references the noop.report-as-issue pattern, but the earlier “No-Op Logging (noop:)” section doesn’t document report-as-issue, so readers won’t know what that comparison means. Either add a short explanation/link to the noop option, or rephrase without relying on an undocumented setting.
| ```yaml wrap | ||
| --- | ||
| permissions: | ||
| contents: read | ||
| engine: claude | ||
| network: defaults | ||
| ... |
There was a problem hiding this comment.
In this frontmatter example, the closing line uses ..., which is a YAML document end marker but not the standard Markdown frontmatter delimiter. For consistency with other workflow examples (which use --- to close frontmatter), consider replacing ... with --- or using a comment (e.g., # ...) to indicate omitted fields so readers don't copy an invalid frontmatter block.
| **Options:** `--json`, `--label`, `--dir/-d` | ||
|
|
||
| The `--dir` flag overrides the local workflow directory. It applies only when `--repo` is not set, consistent with other commands such as `validate`, `fix`, and `add`. |
There was a problem hiding this comment.
The list command supports remote listing via --repo/-r and --path (see pkg/cli/list_workflows_command.go:41-76), but this section’s options list omits those flags while the text references --repo. Consider adding --repo/-r (and --path) to the documented options/examples so readers can actually use --dir vs --path correctly for local vs remote repos.
|
|
||
| **Options:** `--parse`, `--json`, `--repo/-r` | ||
|
|
||
| The `--repo` flag accepts `owner/repo` format and is required when passing a bare numeric run ID without a full URL, allowing the command to locate the correct repository. |
There was a problem hiding this comment.
This paragraph says --repo is required when passing a bare numeric run ID, but audit can resolve {owner}/{repo} from the current repo context when owner/repo aren’t provided (see fetchWorkflowRunMetadata in pkg/cli/audit.go:614-620). Suggest rewording to clarify that --repo is only needed when auditing a run outside the current repository context (or when the run ID alone is ambiguous).
Documentation Updates - 2026-03-10
This PR updates the documentation based on features merged in the last 24 hours.
Features Documented
run,audit,new, andlistcommands (from Add missing flags to run, audit, new, and list commands for CLI consistency #20272)report-failure-as-issuesafe-outputs option (from Improve failure issue actionability with generic debug prompt and report-failure-as-issue option #20266)Changes Made
docs/src/content/docs/setup/cli.md:gh aw run --json / -j: documents new JSON output flag that emits a JSON array of triggered workflow results to stdoutgh aw audit --repo / -r: documents new flag for specifyingowner/repowhen passing a bare numeric run IDgh aw new --engine / -e: documents new flag to injectengine:into the generated frontmatter templategh aw list --dir / -d: documents new flag for overriding the local workflow directory (consistent withvalidate,fix,add)docs/src/content/docs/reference/safe-outputs.md:Failure Issue Reporting (report-failure-as-issue:)section under Global Configuration Optionsreport-failure-as-issue: falseto suppress automatic failure issue creation per workflow (defaults totrue)Merged PRs Referenced
Not Requiring Documentation
repos: public— already documented ingithub-tools.mdconcurrency.job-discriminatorto prevent fan-out cancellations in job-level concurrency groups #20190 -concurrency.job-discriminator— already documented inreference/concurrency.mdandreference/frontmatter-full.mdpull_request_targetas valid PR context increate_pull_request_review_comment#20268, [log] Add debug logging to artifact manager, update command, and MCP config utils #20261 - Internal fixes and logging changes