Skip to content

[docs] Update documentation for features from 2026-05-16 #32605

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

Closed
github-actions wants to merge 2 commits into from
Closed

[docs] Update documentation for features from 2026-05-16 #32605

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ee8ed70
[docs] Document centralized slash-command dispatch input behavior and…
github-actions[bot] May 16, 2026
2e79dc1
docs: remove incorrect @copilot mention-preservation note
Copilot May 16, 2026
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
2 changes: 2 additions & 0 deletions docs/src/content/docs/reference/command-triggers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,6 +84,8 @@ on:

**Note**: With default inline strategy, you cannot combine `slash_command` with `issues`, `issue_comment`, or `pull_request` as they would conflict. With `strategy: centralized`, non-slash events are preserved because slash matching is handled in the generated central trigger workflow.

**`workflow_dispatch` inputs under centralized routing**: Centralized slash-command workflows are invoked by the generated router rather than by manual `workflow_dispatch` callers. To keep router-dispatched runs compatible, any `workflow_dispatch.inputs.<name>.required: true` declared in a centralized workflow's source frontmatter is normalized to `required: false` in the compiled lock file. Inputs remain available — they just are not enforced as required by the dispatch schema.

**Exception for Label-Only Events**: You CAN combine `slash_command` with `issues` or `pull_request` if those events are configured for label-only triggers (`labeled` or `unlabeled` types only). This allows workflows to respond to slash commands while also reacting to label changes.

### Combining `slash_command` with `bots:`
Expand Down