Exclude docker build report artifact from release packing #1042
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
|
Perfect. Much thanks for the quick response! |
|
You latest changes are included in https://github.com/rmcrackan/Libation/releases/tag/v11.5.4 |
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.
When I redid the docker build process, it added a new artifact to the workflow that contains a report on the docker image that was built. This was causing an error when the release process was trying to download all of the artifacts for the release. This PR adds a pattern to include only the artifacts that should get included in the release.
You can see a successful run of the fixed workflow at https://github.com/pixil98/Libation/actions/runs/11846675142