docs(hub): document required output contracts (#2948)
* 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:
@@ -44,7 +44,7 @@ Dispatch fails and the event is recorded as failed. Nothing is queued, so trigge
|
||||
|
||||
## Can an agent reply back to Slack or Discord?
|
||||
|
||||
Yes, with `allow_outputs`. It gets one plain-text thread reply per execution. On GitHub, agents reply through the scoped `GH_TOKEN` they already have, so `gh issue comment` works.
|
||||
Yes, with `allow_outputs`. See the [`hub.yml` output capability reference](/docs/hub/configuration/hub-yml#output-capabilities) for reply limits and required outputs. On GitHub, agents reply through the scoped `GH_TOKEN` they already have, so `gh issue comment` works.
|
||||
|
||||
## Can I use it without GitHub?
|
||||
|
||||
|
||||
Reference in New Issue
Block a user