[plan] Add path-filtered pull_request trigger example to create-agentic-workflow.md

[github-actions]

Objective

Add a path-filtered pull_request trigger example to .github/aw/create-agentic-workflow.md for Backend/QA scenarios that need to react to changes in specific file paths.

Context

From agent persona exploration discussion #29038, S1 (Backend Engineer: DB Schema Review) scored 4.4/5. The pull_request trigger with paths filtering is supported but not exemplified. Backend engineers routinely need to trigger workflows only when specific files change (e.g., db/migrations/*.sql, src/api/**).

Approach

1. In .github/aw/create-agentic-workflow.md, find the pull_request trigger documentation
2. Add a frontmatter snippet showing path filtering:
   • on.pull_request.paths with realistic patterns like 'db/migrations/*.sql' or 'schema/**'
3. Optionally add a paths-ignore example to show both patterns
4. Include a brief explanation of when to use path filters vs. no filters

Acceptance Criteria

• At least one path-filtered pull_request example is added
• Example uses a realistic file path pattern (e.g., migrations, API files)
• Documentation is placed near the existing pull_request trigger guidance

Generated by Plan Command for issue #discussion #29038 · ● 280.5K · ◷

• expires on May 1, 2026, 5:04 AM UTC

[github-actions]

🍪 *Issue Monster selected this for Copilotecho BEGIN___COMMAND_OUTPUT_MARKER ; PS1= ; PS2= ; unset HISTFILE ; EC=0 ; echo ___BEGIN___COMMAND_DONE_MARKER___0 ; }

I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.

If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

Caution

Security scanning requires review for Issue Monster

Details

Potential security threats were detected in the agent output. The workflow output should be reviewed before merging.

Review the workflow run logs for details.

🍪 Om nom nom by Issue Monster · ● 16.2K · ◷