Feature/workflow outputs for archives #114
Merged
Conversation
This file contains 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
tyrann0us
reviewed
Mar 12, 2024
tyrann0us
approved these changes
Mar 14, 2024
|
Relates to #98 |
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.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feature
What is the current behavior? (You can also link to an open issue here)
I had previously assumed that writing to the job output would mean that calling workflows can consume the archive name for further handling (->downloading/extracting it again to make further changes).
However, I overlooked that for this to work, you must also define
workflow_call.outputsWhat is the new behavior (if this is a feature change)?
workflow_call.outputsare now defined to pass on the job output to the outside world.Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information: