You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 10, 2022. It is now read-only.
In the docs it say to use DEV_LIB_SKIP=phpunit git commit to ignore phpunit, but that fails because the git commit portion doesn't seem accurate. Shouldn't it just be DEV_LIB_SKIP=phpunit?
The text was updated successfully, but these errors were encountered:
When you prefix a shell command with an environment variable in that way, the environment variable is set during the life of that one command and then is removed. In other words:
That makes sense but is not clear. The context in which it’s being used is likely in the .dev-lib file not in the command line. So I could see it confusing people.
The context in which it’s being used is likely in the .dev-lib file not in the command line.
@valendesigns Could you please elaborate on that? Are you saying that setting DEV_LIB_SKIP in .dev-lib doesn't work? Or should we just include an example of DEV_LIB_SKIP in the Environment Variables section of the readme?
kasparsd
changed the title
Using DEV_LIB_SKIP
DEV_LIB_SKIP documentation
Mar 24, 2019
I’m suggesting we add an example somewhere for using it in the environment file because that’s the context it’s being spoken about. However, the example we show is for the command line and would confuse someone that didn’t know better.
In the docs it say to use
DEV_LIB_SKIP=phpunit git commit
to ignorephpunit
, but that fails because thegit commit
portion doesn't seem accurate. Shouldn't it just beDEV_LIB_SKIP=phpunit
?The text was updated successfully, but these errors were encountered: