We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
enable tmate
After some research, it seems like input values are still strings, even if their type is boolean: https://github.blog/changelog/2021-11-10-github-actions-input-types-for-manual-workflows/. Also https://github.com/orgs/community/discussions/29796. We have to account for that in our workflow file.
boolean
[I'm still not sure why if: ${{ input.enable_tmate }} would have a problem. I thought GitHub action ifs coerced that type of value.]
if: ${{ input.enable_tmate }}
if
The text was updated successfully, but these errors were encountered:
plocket
Successfully merging a pull request may close this issue.
After some research, it seems like input values are still strings, even if their type is
boolean
: https://github.blog/changelog/2021-11-10-github-actions-input-types-for-manual-workflows/. Also https://github.com/orgs/community/discussions/29796. We have to account for that in our workflow file.[I'm still not sure why
if: ${{ input.enable_tmate }}
would have a problem. I thought GitHub actionif
s coerced that type of value.]The text was updated successfully, but these errors were encountered: