fix: don't require ARTIFACT_NAME with multiple specs
#181
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
|
@oliverdunk FYI. No longer require to update workflows to define |
github-actions bot
added a commit
that referenced
this pull request
Apr 17, 2024
SHA: e690b1b Reason: push, by sidvishnoi Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
|
Thanks @sidvishnoi! Much more polished :) |
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.
Automatically generate artifact name based on source. Respect
ARTIFACT_NAMEset in inputs, as added in #180.So that #173 will no longer be a breaking as mentioned
v2.11.2.The artifact name may change from
spec-prod-resulteven with single spec, though some effort was made to keep it stable (i.e. if source isindex.htmlorindex.bs). The automatic name will still start withspec-prod-result.Preview | Diff