refactor(ci): read issue event data directly from the event payload - #597
Merged
Merged
Conversation
The issue analysis workflow resolved issue fields in a dedicated step that wrote them to $GITHUB_OUTPUT, then read them back as step outputs in the two steps that consume them. Each of those steps can read github.event.issue.* directly in its own env: block, so the intermediate step and the output roundtrip are no longer needed. Label joining moves from jq to the join() expression, and the inputs the analysis script receives are unchanged. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: dea12e61-7e4a-46d7-af68-c3df58f18ce6
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The workflow refactor preserves the existing interface with no unresolved issues.
Pull request overview
Refactors the issue-analysis workflow to read issue data directly from the GitHub event payload.
Changes:
- Removes the intermediate issue-resolution step.
- Passes issue metadata through step environment variables.
- Replaces
jqlabel formatting withjoin().
File summaries
| File | Description |
|---|---|
.github/workflows/issue-analysis.yml |
Simplifies issue metadata propagation while preserving required script inputs. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Lily Du (lilyydu)
approved these changes
Sep 16, 2026
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.
The
Issue Analysis → Teamsworkflow had aResolve issue detailsstep that copied fields off the issue event into$GITHUB_OUTPUTso the two steps that actually use them could read them back assteps.issue.outputs.*.That indirection isn't needed. Both consuming steps can read
github.event.issue.*directly in their ownenv:block, so this drops the intermediate step and wires the values straight through.Changes
Resolve issue detailsstep.Analyze issue with Copilot CLItakesISSUE_NUMBERfromgithub.event.issue.numberinenv:rather than assigning it inside the script.Triage and notify Teamsreads its sixISSUE_*values fromgithub.event.issue.*.jqcall to thejoin()expression.Notes
The analysis script's interface is unchanged. It still reads
ISSUE_NUMBER,ISSUE_TITLE,ISSUE_AUTHOR,ISSUE_HTML_URL,ISSUE_LABELSandISSUE_BODYfrom the environment and still splits labels on commas, andjoin(github.event.issue.labels.*.name, ',')produces the same comma-joined stringjqdid. Verified that the workflow still parses and that nosteps.issuereferences remain.