-
Notifications
You must be signed in to change notification settings - Fork 503
New issue
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
Allow --unstable
to be passed through via environment variables
#1575
Comments
This would also be useful for calling |
I think using a directive like
How long do you think the '!include' directive should stay as 'unstable' ? @casey |
Fixed in #1588! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be great if users can globally opt-in to unstable features by setting an environment variable such as
JUST_ALLOW_UNSTABLE
.If that variable is set to any value, it acts the same as if the
--unstable
flag is passed through to the commands.This still allows the safety of feature-flagging the newest commands, but those who want the absolute latest-and-greatest can set this option system-wide and not have to think about passing through the
--unstable
parameterThe text was updated successfully, but these errors were encountered: