Skip to content
This repository has been archived by the owner on Nov 10, 2022. It is now read-only.

DEV_LIB_SKIP documentation #296

Open
valendesigns opened this issue Mar 11, 2019 · 4 comments
Open

DEV_LIB_SKIP documentation #296

valendesigns opened this issue Mar 11, 2019 · 4 comments

Comments

@valendesigns
Copy link
Contributor

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?

@westonruter
Copy link
Contributor

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:

$ DEV_LIB_SKIP=phpunit
$ git commit
(not running phpunit)
$ echo $DEV_LIB_SKIP
phpunit

Whereas:

$ DEV_LIB_SKIP="nothing!"
$ DEV_LIB_SKIP=phpunit git commit
(still not running phpunit)
$ echo $DEV_LIB_SKIP
nothing!

Similarly, for setting NODE_ENV when running node: https://stackoverflow.com/a/9204973/93579

@valendesigns
Copy link
Contributor Author

valendesigns commented Mar 11, 2019 via email

@kasparsd
Copy link
Contributor

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 kasparsd changed the title Using DEV_LIB_SKIP DEV_LIB_SKIP documentation Mar 24, 2019
@valendesigns
Copy link
Contributor Author

valendesigns commented Mar 24, 2019 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants