feat: set env vars for outputs - #31
Open
jenseng wants to merge 9 commits into
Open
Conversation
jenseng
force-pushed
the
env-outputs
branch
9 times, most recently
from
December 20, 2025 01:12
65596e9 to
8d87457
Compare
jenseng
force-pushed
the
env-outputs
branch
8 times, most recently
from
December 20, 2025 06:56
4180ea6 to
21eec31
Compare
jenseng
force-pushed
the
env-outputs
branch
2 times, most recently
from
January 6, 2026 18:03
3781705 to
3c067d9
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.
Fixes #17
Optionally set env vars for each of the action's outputs. This provides a simpler method to access outputs than the default
fromJSONapproach.For example, instead of:
You can set
env-outputs: truelike so:For more control over the output variable names and how to deal with potential conflicts, see the new
env-outputs-prefix,env-outputs-upcase, andenv-outputs-on-conflictoptions documented in the README, metadata file, and tests.