Work around GitHub false-positive for passing secret to another action #3396
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.
Infuriatingly, GitHub thinks that the string
[]
or any string containing any sort of hash contains a secret. Therefore, we can't just simply pass[]
to the outputs of the first job in the workflow.This is a little hack to output either the string "true" or the string "false" instead.
Also, just updating the base android build script to support manual deployment of a testflight client for Android.