docs: expand slash command event filtering documentation

[Copilot]

Default slash_command triggers generate listeners for all event types, causing skipped runs in the Actions UI for workflows that only apply to specific contexts (e.g., issue-only bug investigation pipelines).

The events: field already exists but the docs underexplained the motivation and usage patterns.

Changes

• reference/command-triggers.md: Expanded "Filtering Command Events" with:
  • Motivation explaining the skipped-run noise problem
  • Compact supported events list
  • Concise issue-only and PR-only yaml examples (no permissions or full frontmatter)
  • Note clarifying issue_comment vs pull_request_comment mapping
• reference/triggers.md: Added inline events: example to the slash_command: section so the feature is discoverable without navigating to the full reference

Example

on:
  slash_command:
    name: investigate
    events: [issues, issue_comment]  # Only issue contexts — no PR-triggered skipped runs

[pelikhan]

@copilot unbloat added docs, do not recommend permissions write

[Copilot]

@copilot unbloat added docs, do not recommend permissions write

Trimmed in b294b2e — replaced full-workflow examples with concise yaml-only snippets, removed all permissions blocks (including issues: write), and condensed the supported events from a table to a single line.

[Copilot]

Pull request overview

Expands documentation around slash_command.events to explain why and how to filter command-trigger contexts, reducing skipped-run noise in the GitHub Actions UI.

Changes:

• Adds an inline events: example to the slash_command: section in the triggers reference.
• Expands “Filtering Command Events” in the command triggers reference with motivation, supported events, concise examples, and an issue_comment vs pull_request_comment mapping note.

Show a summary per file

File	Description
docs/src/content/docs/reference/triggers.md	Adds a discoverable events: example under slash_command: to encourage context filtering.
docs/src/content/docs/reference/command-triggers.md	Expands event filtering docs with motivation, supported events list, mapping note, and shorter examples.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comments suppressed due to low confidence (1)

docs/src/content/docs/reference/command-triggers.md:105

• The section title “Example command workflow” is followed by yaml snippets that only show an on: block (not a complete workflow markdown/frontmatter example). Consider renaming the heading to reflect that these are event-filtering examples/config snippets, or switch the examples back to a full aw workflow format if “workflow” is meant literally.

### Example command workflow

Issue-only command (avoids skipped runs from PR events):

```yaml wrap

• Files reviewed: 2/2 changed files
• Comments generated: 2