Replies: 1 comment
-
Couldn't agree more with this. Every flag should be configurable via env. variables too. I moved this to an issue. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
It would be great to expose commands parameters such as
--configuration
or--no-open
as env vars. For instance, whengenerate
is run inside a CI/CD job it is obvious that we prefer to enable--no-open
in this case.Vars could be prefixed with
TUIST_
, here are some of my homemade envs:TUIST_CONFIGURATION
: when set add option--configuration $TUIST_CONFIGURATION
TUIST_NO_OPEN
: when set add the flag--no-open
to the generate commandTUIST_NO_BINARY_CACHE
: same as above but with--no-binary-cache
TUIST_GENERATE_PATH
TUIST_GENERATE_SOURCES
TUIST_CLEAN_CATEGORIES
TUIST_TEST_PLATFORM
TUIST_TEST_OS
TUIST_TEST_SCHEMES
I have implemented such behavior in my own scripts but I think it could benefit to more Tuist users that face this need.
Beta Was this translation helpful? Give feedback.
All reactions