jb/paseo
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

docs(hub): document required output contracts (#2948)

Browse Source 
* docs(hub): document required output contracts

* docs(hub): link faq to output contract

* docs(hub): document materializable required outputs

Explain that required declarations resolve through registered capabilities, failed deliveries can be retried, and command-line repository comments use the scoped credential path.
This commit is contained in:
Mohamed Boudra
2026-08-06 22:44:25 +02:00
committed by GitHub
parent 1e03e2d120
commit ef6d7b3b9a
3 changed files with 27 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
public-docs/hub/triggers/index.md
+1 -1
View File
@@ -88,4 +88,4 @@ Both run. Triggers are not ordered and do not shadow each other, in one configur
## Replying
Put `allow_outputs` on the step that should reply. The available provider reply types are `slack.reply`, `discord.reply`, and `github.reply`; set `max` when a step needs more than one update. GitHub-triggered agents also receive a scoped GitHub credential for `gh`.
Put `allow_outputs` on the step that should reply. The Hub provider reply capabilities are `slack.reply` and `discord.reply`; set `max` when a step needs more than one update, or `required: true` when it must emit at least one reply before it can finish. A required type must be registered and available for the execution context. GitHub-triggered agents receive a scoped GitHub credential for `gh` and can comment through that credential instead of a Hub output tool. See the [`hub.yml` output capability reference](/docs/hub/configuration/hub-yml#output-capabilities) for the contract.