Tighten workflow authoring guidance for trigger selection, scenario mapping, and visual-regression network scope#39119
Merged
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update agent persona exploration insights
Tighten workflow authoring guidance for trigger selection, scenario mapping, and visual-regression network scope
Jun 13, 2026
pelikhan
approved these changes
Jun 13, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates gh-aw authoring documentation to make trigger selection and common workflow scenarios easier to choose, and adds explicit guidance for minimizing network exposure in visual regression workflows.
Changes:
- Added a concise
workflow_runvsdeployment_statusrule-of-thumb and reiterated single-job constraints in monitoring patterns. - Added compact “scenario example” mappings to the workflow creation guide (schema review, visual regression, deployment triage, stakeholder digest).
- Added a network-minimization reminder section to the visual regression reference (with additional guardrails for previews and Playwright navigation).
Show a summary per file
| File | Description |
|---|---|
.github/workflows/test-quality-sentinel.lock.yml |
Updates generated workflow metadata and adjusts safe-output success messaging template. |
.github/aw/workflow-patterns.md |
Adds explicit trigger decision guidance (workflow_run vs deployment_status) plus single-job constraint reminders. |
.github/aw/visual-regression.md |
Adds a “Network-Minimization Reminders” section for safer visual regression workflows. |
.github/aw/create-agentic-workflow.md |
Adds compact scenario examples to speed up initial workflow authoring decisions. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 4/4 changed files
- Comments generated: 2
|
|
||
| - Prefer local preview serving (`localhost`/`127.0.0.1`) over external preview environments when possible. | ||
| - If external previews are required, allowlist only exact preview domains needed for the check (avoid broad wildcards). | ||
| - Enable `network.node` only when the workflow actually installs/builds Node dependencies; scope domains to package registries and required preview hosts. |
| env: | ||
| GH_AW_WORKFLOW_NAME: "Test Quality Sentinel" | ||
| GH_AW_SAFE_OUTPUT_MESSAGES: "{\"footer\":\"\\u003e 🧪 *Test quality analysis by [{workflow_name}]({run_url})*{ai_credits_suffix}{history_link}\",\"runStarted\":\"🔬 [{workflow_name}]({run_url}) is analyzing test quality on this {event_type}...\",\"runSuccess\":\"🧪 [{workflow_name}]({run_url}) completed test quality analysis.\",\"runFailure\":\"❌ [{workflow_name}]({run_url}) {status} during test quality analysis.\"}" | ||
| GH_AW_SAFE_OUTPUT_MESSAGES: "{\"footer\":\"\\u003e 🧪 *Test quality analysis by [{workflow_name}]({run_url})*{ai_credits_suffix}{history_link}\",\"runStarted\":\"🔬 [{workflow_name}]({run_url}) is analyzing test quality on this {event_type}...\",\"runSuccess\":\"✅ [{workflow_name}]({run_url}) completed test quality analysis.\",\"runFailure\":\"❌ [{workflow_name}]({run_url}) {status} during test quality analysis.\"}" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Persona exploration showed strong baseline guidance but identified three doc gaps: compact scenario examples in workflow creation, clearer
deployment_statusvsworkflow_runselection, and explicit network-minimization guidance for visual regression workflows. This PR updates those references to make authoring decisions faster and more consistent.Workflow creation guidance (
.github/aw/create-agentic-workflow.md)noopbehavior in these scenarios.Monitoring trigger decisioning (
.github/aw/workflow-patterns.md)workflow_runfor GitHub Actions outcomes in-repodeployment_statusfor external deployment providers via Deployments APIVisual regression network posture (
.github/aw/visual-regression.md)network.nodeonly when build/install is needed