[plan] Add workflow_run vs pull_request trigger decision guide to documentation #29785

Objective

Add a clear decision guide explaining when to use workflow_run vs pull_request triggers in agentic workflows.

Context

From discussion #29782 — Agent Persona Exploration identified that workflow_run is consistently preferred over pull_request for artifact-dependent tasks (coverage reports, CI diagnostics), but this is not documented clearly for users.

Approach

1. Locate the appropriate documentation file (likely .github/aw/create-agentic-workflow.md or docs)
2. Add a Choosing the Right Trigger section with a decision guide:
   • Use pull_request when: direct access to PR diff/code, no CI artifact dependency, fork PRs are OK with read-only
   • Use workflow_run when: task depends on CI artifacts (logs, coverage reports), fork PRs need write permissions, post-CI analysis
3. Include a short table or flowchart summarizing the decision
4. Note that workflow_run fires in the base repo context, giving full permissions even for fork PRs

Files to Modify

• .github/aw/create-agentic-workflow.md (or relevant docs file)

Acceptance Criteria

• Decision guide added explaining workflow_run vs pull_request
• Key distinction documented: workflow_run required for CI artifacts and fork PR write access
• At least one concrete example showing a workflow_run trigger configuration

Generated by Plan Command for issue #discussion #29782 · ● 313.9K · ◷

• expires on May 4, 2026, 3:56 PM UTC