[docs] Update documentation for features from 2026-08-06 - #50832
Merged
Conversation
Contributor
Author
There was a problem hiding this comment.
Threat detection produced a warning for this pull request output.
These changes need to be scrutinized before merge and only merged after a careful manual review.
- Detection reason:
agent_failure - Review workflow run logs: https://github.com/github/gh-aw/actions/runs/31096972469
Contributor
Author
|
🎉 This pull request is included in a new release. Release: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Warning
Threat Detection Engine Failure — The analysis engine could not complete. This is a tooling failure, not a security finding.
What happened
The threat detection engine failed to produce results.
Review the workflow run logs for details.
Overview
Documentation-only update describing two recently added behaviors: explicit trial success/failure signaling and a workflow-level
report-failed-jobscontrol undersafe-outputs:. No code changes; no breaking changes.Key Changes
docs/src/content/docs/experimental/trial-ops.mdsuccessandsafe_output_errorsfields in thegh aw trialJSON result schema.gh aw trialnow exits non-zero when safe-output processing rejects one or more requested actions, rather than always reporting success.safe_output_errorsinstead of generic "no errors in logs".docs/src/content/docs/reference/frontmatter.mdsafe-outputs:accepts workflow-level control fields (not just per-handler config), usingreport-failed-jobs: falseas an example to disable the automatic failed-job reporting issue.report-failed-jobsdefaults totruewhen omitted.Impact
docs/**/*.md)