Skip to content
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

[Bug?]: yarn-cli does not recognize "CI=false" #6375

Closed
1 task
smartrejames opened this issue Jul 3, 2024 · 0 comments · Fixed by #6377
Closed
1 task

[Bug?]: yarn-cli does not recognize "CI=false" #6375

smartrejames opened this issue Jul 3, 2024 · 0 comments · Fixed by #6377
Labels
bug Something isn't working

Comments

@smartrejames
Copy link

Self-service

  • I'd be willing to implement a fix

Describe the bug

yarn-cli does not recognize the environment variable CI=false. This leads to unexpected behavior when trying to run certain commands in environments where CI is not set to true.

To reproduce

  1. Open a terminal.
  2. Set the environment variable CI to false: export CI=false
  3. Run any yarn-cli command that should be affected by the CI environment variable, for example:
    remove yarn.lock && yarn install
    

Environment

System:
    OS: macOS 14.5
    CPU: (10) arm64 Apple M1 Pro
  Binaries:
    Node: 20.15.0 - /private/var/folders/vp/v2gwm71s16b16xg4w444zjjm0000gn/T/xfs-da6c39be/node
    Yarn: 4.3.1 - /private/var/folders/vp/v2gwm71s16b16xg4w444zjjm0000gn/T/xfs-da6c39be/yarn
    npm: 10.7.0 - /opt/homebrew/opt/node@20/bin/npm

Additional context

No response

@smartrejames smartrejames added the bug Something isn't working label Jul 3, 2024
@arcanis arcanis closed this as completed in 35167b2 Jul 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant