Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .github/aw/cli-commands.md
Original file line number Diff line number Diff line change
Expand Up @@ -223,6 +223,7 @@ Update imported shared workflow components.
```bash
gh aw update # Update all workflows from source
gh aw update <workflow-name> # Update a specific workflow
gh aw update <package-url-or-name> # Update all workflows installed from a package
gh aw update --major # Allow major version updates
gh aw update --create-pull-request # Update and open a PR (alias: --pr)
gh aw update --repo owner/repo # Update workflows in another repository (isolated shallow checkout)
Expand Down
2 changes: 2 additions & 0 deletions .github/aw/safe-outputs-runtime.md
Original file line number Diff line number Diff line change
Expand Up @@ -184,6 +184,8 @@ The `report-incomplete` safe-output is enabled by default and is distinct from `
- `footer:` - Global footer control for all safe outputs (boolean, default: `true`)
- When `false`, omits visible AI-generated footer content from all created/updated entities (issues, PRs, discussions, releases) while still including XML markers for searchability
- Individual safe-output types can override this setting
- `body-footer:` - Deterministic template appended to every body-producing safe output, additive with any handler-specific `body-footer:` (string)
- Appended even when `footer: false` omits the AI-generated footer
- `staged:` - Preview mode for all safe outputs (boolean)
- When `true`, emits step summary messages instead of making GitHub API calls; useful for testing without side effects
- `env:` - Environment variables passed to all safe output jobs (object)
Expand Down
1 change: 1 addition & 0 deletions .github/aw/safe-outputs.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,3 +19,4 @@ Safe outputs are the write path for agentic workflows. Keep the main agent job r
- Always scope mutating operations as tightly as possible.
- For pull-request or branch mutation, always restrict `allowed-files`.
- Use `noop` when no visible change is required after successful execution.
- `target:` is enforced, not merely validated: when set to `"triggering"` or a fixed number, any issue/PR number the agent supplies in its JSON output (including temporary-id references) is ignored in favor of the configured target. Only `target: "*"` lets the agent's own output select which issue/PR is affected.
Loading