gh-actions: fix hard-coded PDF name in deploy action, part 2 #1241
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
github-actions
bot
added
the
Component: Workflows
bwbohl
approved these changes
Jun 27, 2023
rettinghaus
approved these changes
Jun 29, 2023
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.
This PR is a follow-up to #1223 because a reference to the hard-coded PDF file name was overlooked. It provides another step for fixing #1125.
However, this reference here cannot be fixed by a wildcard glob since globs do not work with linux copy command
cp. For that reason, the copy command gets piped through afindthat will lookup the wildcard file name and hand it over to thecpprocess.Finding and copying worked fine locally, we have to check how it works in the CI environment.