Due to testing always being different per developer, it makes sense to
turn all the inputs into environmentals which can then live in the
.bitrise.secrets.yml file. This prevents a developer needing to modify
the bitrise.yml file with their specific test settings and risk
committing to the repo alongside other code changes.
I've based this PR against upstream master to keep it isolated from PR #15, but will rebase as required depending on which PRs get merged and in what order.
Due to testing always being different per developer, it makes sense to turn all the inputs into environmentals which can then live in the .bitrise.secrets.yml file. This prevents a developer needing to modify the bitrise.yml file with their specific test settings and risk committing to the repo alongside other code changes.
I've based this PR against upstream master to keep it isolated from PR #15, but will rebase as required depending on which PRs get merged and in what order.