-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
feat(core): don't clear NX_BASE or NX_HEAD #20125
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit f765c3b. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution
✅ Successfully ran 5 targets
Sent with 💌 from NxCloud. |
f765c3b
to
469d67d
Compare
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 469d67d. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 6 targets
Sent with 💌 from NxCloud. |
(cherry picked from commit f9009e9)
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Current Behavior
When I try to access the
NX_BASE
environment variable that I set in CI from a local executor it returnsundefined
Expected Behavior
I can access the
NX_BASE
value that I set in CI within a local executorRelated Issue(s)
The behavior was added in #10523 however it is unclear why it was necessary. As far as I can tell Nx does not write to these environment variables. The nearby comment says that they are being reset in case Nx is called within Nx however I precisely do not want them reset so that I can call Nx within Nx and re-use the same base and head
This is tangentially related to this discord question