CI: Fix loss of number type when calling reusable workflow #1239
+2
−1
Conversation
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
The workflow_dispatch break_duration input has a type of 'number', but this somehow gets lost when calling the reusable workflow. We see the following error: The template is not valid. .github/workflows/stackhpc-multinode.yml (Line: 64, Col: 23): Unexpected value '60' This issue is described in https://github.com/orgs/community/discussions/67182. We use the fromJSON workaround in the thread.
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.
The workflow_dispatch break_duration input has a type of 'number', but
this somehow gets lost when calling the reusable workflow. We see the
following error:
The template is not valid. .github/workflows/stackhpc-multinode.yml
(Line: 64, Col: 23): Unexpected value '60'
This issue is described in
https://github.com/orgs/community/discussions/67182. We use the fromJSON
workaround in the thread.