docs: add workflow_run trigger examples for DevOps monitoring workflows#29060
Closed
docs: add workflow_run trigger examples for DevOps monitoring workflows#29060
Conversation
5 tasks
Add a new "Creating Monitoring Workflows" section to .github/aw/create-agentic-workflow.md placed after "Creating Command Workflows". The section includes: - Intro explaining workflow_run for GitHub Actions-internal monitoring - Clarification on deployment_status vs workflow_run distinction - Key context variables table (conclusion, name, id, html_url, head_branch, commit message) - Example 1: minimal CI failure notification (no pre-steps) - Example 2: full DevOps monitoring with log fetching, root-cause analysis, and dedup - Guidance for when to use workflow_run vs deployment_status - Agent guidance for responding to DevOps monitoring requests Closes #<issue> Agent-Logs-Url: https://github.com/github/gh-aw/sessions/71971270-4764-4836-beee-b7c0d1e6e7bd Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com>
Agent-Logs-Url: https://github.com/github/gh-aw/sessions/71971270-4764-4836-beee-b7c0d1e6e7bd Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add workflow_run trigger examples to create-agentic-workflow.md
docs: add workflow_run trigger examples for DevOps monitoring workflows
Apr 29, 2026
This was referenced Apr 29, 2026
Closed
Copilot AI
added a commit
that referenced
this pull request
Apr 29, 2026
- Compile on.workflow_run.conclusion (string|string[]) into a job if condition that guards conclusion matching, guarded by event_name check so the condition remains transparent for other triggers (e.g. workflow_dispatch) - Comment out the conclusion field in the YAML on: section with explanatory comment, tracking inWorkflowRunConclusionArray to avoid false matches on workflows:/types: array items - Add workflow_run_conclusion to aw_context passed to workflow_call so called workflows can access the triggering run's conclusion - Add gh-aw.workflow_run.conclusion OTEL attribute to setup and conclusion spans in send_otlp_span.cjs, reading from awInfo or aw_context propagation - Add workflow_run_conclusion to generate_aw_info.cjs for direct event access - Add "Creating Monitoring Workflows" section to create-agentic-workflow.md (from PR #29060), updated to use on.workflow_run.conclusion instead of manual if: condition - Add unit tests: TestExtractWorkflowRunConclusionCondition, TestExtractIfConditionMergesWorkflowRunConclusion, TestWorkflowRunConclusionCommentedInYAML Agent-Logs-Url: https://github.com/github/gh-aw/sessions/7cab4a8f-bc7a-47f5-9cc5-79d5593830fb Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
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.
workflow_runwas mentioned 4 times increate-agentic-workflow.mdwith no complete examples, leaving DevOps monitoring scenarios (CI/CD failure detection, deployment alerting) poorly served.Changes
deployment_statusvsworkflow_rundistinction calloutconclusion,id,html_url,head_branch,head_commit.message)workflow_run+if: conclusion == 'failure'that posts a PR comment; no pre-steps--log-failedlogs, usescache-memoryfor run deduplication, and instructs the agent to post a root-cause commentExample 2 frontmatter shape: