jq: Remove redundant process.env assignment for multiline values #3459
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 jq action was directly assigning to
process.env[env_var]before callingcore.exportVariable(), which breaks multiline values since direct assignment doesn't use EOF delimiters.Changes
Removed redundant
process.envassignment insrc/action.tsline 29core.exportVariable()already handles environment variable persistence correctly with multiline supportAdded multiline test coverage in
__tests__/action.test.tsexportVariableis called with multiline contentprocess.envis not directly modifiedUpdated existing test to expect correct behavior (no direct process.env assignment)
Before
After
When jq outputs multiline content,
core.exportVariable()writes toGITHUB_ENVwith proper delimiters:Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.