fix: pass drift data via step outputs — agent can't access activation filesystem#664
Merged
fix: pass drift data via step outputs — agent can't access activation filesystem#664
Conversation
steps: runs in activation job (different runner than agent). Files written there don't persist to the agent's filesystem. Fix: Use $GITHUB_OUTPUT to pass JSON from steps to the prompt via template substitution. The agent sees data inline — no cat, no file paths, no filesystem dependency. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
d9299ed to
8ef5e73
Compare
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.
Third iteration fixing the instruction-drift workflow.
Problem chain:
steps:(activation job) → scripts ran with GH_TOKEN ✅ but files written to activation filesystem aren't available in agent job (different runner)$GITHUB_OUTPUT→ template substitution inlines JSON directly into the agent promptHow it works now:
The agent sees the actual JSON data right in its prompt — no
catcommands, no file paths, no filesystem dependency.