Skip to content

[docs] Update documentation for features from 2026-02-22 #17647

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pelikhan merged 1 commit into from
Feb 22, 2026
+8 −0
Merged

[docs] Update documentation for features from 2026-02-22 #17647

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 6 additions & 0 deletions docs/src/content/docs/reference/safe-outputs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -236,6 +236,8 @@ safe-outputs:
allowed-reasons: [outdated] # restrict hiding reasons (optional)
```

The author of the parent issue, PR, or discussion receiving the comment is automatically preserved as an allowed mention. This means `@username` references to the issue/PR/discussion author are not neutralized when the workflow posts a reply.
Copy link

Copilot AI Feb 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This states the parent issue/PR/discussion author is “automatically preserved as an allowed mention”. In the implementation, bot authors are intentionally excluded from the allowlist, so @bot-author mentions may still be neutralized. Consider clarifying this (e.g., “non-bot author”) to avoid overstating the guarantee.

Suggested change
The author of the parent issue, PR, or discussion receiving the comment is automatically preserved as an allowed mention. This means `@username` references to the issue/PR/discussion author are not neutralized when the workflow posts a reply.
The non-bot author of the parent issue, PR, or discussion receiving the comment is automatically preserved as an allowed mention. This means `@username` references to that non-bot issue/PR/discussion author are not neutralized when the workflow posts a reply; mentions of bot authors may still be neutralized.

Copilot uses AI. Check for mistakes.

#### Hide Older Comments

Set `hide-older-comments: true` to minimize previous comments from the same workflow (identified by `GITHUB_WORKFLOW`) before posting new ones. Useful for status updates. Allowed reasons: `spam`, `abuse`, `off_topic`, `outdated` (default), `resolved`.
Expand Down Expand Up @@ -835,6 +837,10 @@ safe-outputs:

When `push-to-pull-request-branch` is configured, git commands (`checkout`, `branch`, `switch`, `add`, `rm`, `commit`, `merge`) are automatically enabled.

#### Fail-Fast on Code Push Failure

If `push-to-pull-request-branch` (or `create-pull-request`) fails, the safe-output pipeline cancels all remaining non-code-push outputs. Each cancelled output is marked with an explicit reason such as "Cancelled: code push operation failed". The failure details appear in the agent failure issue or comment generated by the conclusion job.
Copy link

Copilot AI Feb 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The cancellation reason in output results includes the failing code-push type and error (e.g., "Cancelled: code push operation failed (push_to_pull_request_branch: Branch not found)"). The docs’ example reason omits that detail; consider mentioning that the reason typically includes the failing output type + error to make it easier for users to recognize what failed.

Suggested change
If `push-to-pull-request-branch` (or `create-pull-request`) fails, the safe-output pipeline cancels all remaining non-code-push outputs. Each cancelled output is marked with an explicit reason such as "Cancelled: code push operation failed". The failure details appear in the agent failure issue or comment generated by the conclusion job.
If `push-to-pull-request-branch` (or `create-pull-request`) fails, the safe-output pipeline cancels all remaining non-code-push outputs. Each cancelled output is marked with an explicit reason, typically including the failing code-push type and error, such as `Cancelled: code push operation failed (push_to_pull_request_branch: Branch not found)`. The failure details also appear in the agent failure issue or comment generated by the conclusion job.

Copilot uses AI. Check for mistakes.

### Release Updates (`update-release:`)

Updates GitHub release descriptions: replace (complete replacement), append (add to end), or prepend (add to start).
Expand Down
2 changes: 2 additions & 0 deletions docs/src/content/docs/setup/cli.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -330,6 +330,8 @@ gh aw audit 12345678 --parse # Parse logs to markdo

Logs are saved to `logs/run-{id}/` with filenames indicating the extraction level (job logs, specific step, or first failing step).

When a workflow fails before the agent executes (for example, due to lockdown validation failures, missing secrets, or binary install failures), the audit report surfaces the actual error from the workflow step log files. The `failure_analysis.error_summary` field reflects the specific failure message rather than reporting "No specific errors identified". Providing an invalid run ID returns a human-readable error instead of a raw exit code.
Copy link

Copilot AI Feb 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The CLI now returns a human-readable error specifically when the workflow run ID is not found (404/Not Found). The wording here says “invalid run ID”, which could be read as a format/parse error. Consider rephrasing to “non-existent run ID” / “run ID not found” (and optionally note this can also happen if you don’t have repo access), to match the actual behavior.

Suggested change
When a workflow fails before the agent executes (for example, due to lockdown validation failures, missing secrets, or binary install failures), the audit report surfaces the actual error from the workflow step log files. The `failure_analysis.error_summary` field reflects the specific failure message rather than reporting "No specific errors identified". Providing an invalid run ID returns a human-readable error instead of a raw exit code.
When a workflow fails before the agent executes (for example, due to lockdown validation failures, missing secrets, or binary install failures), the audit report surfaces the actual error from the workflow step log files. The `failure_analysis.error_summary` field reflects the specific failure message rather than reporting "No specific errors identified". Providing a non-existent run ID, or a run ID for a repository you don't have access to, returns a human-readable error instead of a raw exit code.

Copilot uses AI. Check for mistakes.

#### `health`

Display workflow health metrics and success rates.
Expand Down