[docs] Update documentation for features from 2026-03-01#18982
Merged
[docs] Update documentation for features from 2026-03-01#18982
Conversation
- Add target/target-repo/allowed-repos to resolve-pull-request-review-thread - Document automatic workflow_call outputs for safe-output types - Mark tools.github guard policy (repos/min-integrity) as experimental Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
github-actions
bot
added
automation
documentation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates reference documentation to reflect newly merged features around safe-outputs and GitHub tools guard policies (2026-03-01 daily doc update).
Changes:
- Document cross-repository configuration fields for
resolve-pull-request-review-threadinsafe-outputs.md. - Add documentation for automatic
workflow_calloutputs exposed from supported safe-output results. - Mark
tools.githubguard policy fields (repos,min-integrity) as experimental via a caution callout.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| docs/src/content/docs/reference/safe-outputs.md | Updates safe-output docs for cross-repo thread resolution and documents workflow_call output injection behavior. |
| docs/src/content/docs/reference/github-tools.md | Adds an “Experimental Feature” caution callout for guard policy fields. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+1230
to
+1232
| When a workflow uses `on: workflow_call` (or includes `workflow_call` in its triggers) and configures safe outputs, the compiler automatically injects `on.workflow_call.outputs` exposing the results of each configured safe output type. This makes gh-aw workflows composable building blocks in larger automation pipelines. | ||
|
|
||
| The following named outputs are exposed for each configured safe output type: |
There was a problem hiding this comment.
The opening sentence implies on.workflow_call.outputs is injected whenever any safe outputs are configured, but the compiler only injects outputs when at least one safe-output type that produces named workflow outputs is configured (currently create-issue, create-pull-request, add-comment, push-to-pull-request-branch). Consider rewording to reflect that limitation so callers don’t expect outputs for other safe output types.
Suggested change
| When a workflow uses `on: workflow_call` (or includes `workflow_call` in its triggers) and configures safe outputs, the compiler automatically injects `on.workflow_call.outputs` exposing the results of each configured safe output type. This makes gh-aw workflows composable building blocks in larger automation pipelines. | |
| The following named outputs are exposed for each configured safe output type: | |
| When a workflow uses `on: workflow_call` (or includes `workflow_call` in its triggers) and configures at least one safe output type that produces named workflow outputs, the compiler automatically injects `on.workflow_call.outputs` exposing the results of those supported safe output types. This makes gh-aw workflows composable building blocks in larger automation pipelines. | |
| The following named outputs are exposed for each configured safe output type that supports `workflow_call` outputs: |
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.
Documentation Updates - 2026-03-01
This PR updates the documentation based on features merged in the last 24 hours.
Features Documented
resolve-pull-request-review-thread(from feat: add target, target-repo, and allowed-repos to resolve-pull-request-review-thread #18891)workflow_calloutputs for safe-output results (from feat: expose safe-output results as workflow_call outputs #18914)tools.githubguard policy fields (from Mark tools.github.repos and tools.github.min-integrity as experimental #18904)Changes Made
Updated
docs/src/content/docs/reference/safe-outputs.md:resolve-pull-request-review-threadsection to addtarget,target-repo,allowed-repos, andgithub-tokenfields with link to cross-repository docs (previously the section stated resolution was scoped to the triggering PR only)on.workflow_call.outputswhen a workflow usesworkflow_call+ safe-outputs (including output name table forcreate-issue,create-pull-request,add-comment, andpush-to-pull-request-branch)Updated
docs/src/content/docs/reference/github-tools.md::::caution[Experimental Feature]callout to the Guard Policies section fortools.github.reposandtools.github.min-integrityMerged PRs Referenced
Already Documented (no action needed)
footer: falsesupport toadd-commentsafe output #18942 (footer: falseforadd-comment) — already documented in safe-outputs.md and FAQcheckout.github-tokentocheckout.tokenfor actions/checkout #18878 (renamecheckout.github-token→checkout.token) — already updated in frontmatter.md and cross-repository.md by the PR itself