fix(misc): prevent nxCloudId from being generated for new workspaces#34532
Merged
fix(misc): prevent nxCloudId from being generated for new workspaces#34532
Conversation
Contributor
|
View your CI Pipeline Execution ↗ for commit 714a599
☁️ Nx Cloud last updated this comment at |
FrozenPandaz
approved these changes
Feb 20, 2026
✅ Deploy Preview for nx-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for nx-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
jaysoo
force-pushed
the
cnw_custom_fix
branch
from
7350a0e to
8d07562
Compare
…[Self-Healing CI Rerun]
![nx-cloud[bot]](https://avatars.githubusercontent.com/in/80458?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Nx Cloud has identified a flaky task in your failed CI:
🔂 Since the failure was identified as flaky, we triggered a CI rerun by adding an empty commit to this branch.
🎓 Learn more about Self-Healing CI on nx.dev
FrozenPandaz
pushed a commit
that referenced
this pull request
Feb 20, 2026
…34532) ## Current Behavior When creating a new workspace using `create-nx-workspace` with the "custom" preset flow, an `nxCloudId` is generated and added to `nx.json`. This happens even though the onboarding flow is supposed to handle Cloud setup separately via a short URL. ## Expected Behavior New workspaces created via `create-nx-workspace` should not have `nxCloudId` set in `nx.json`. Instead, a short URL is provided for users to finish Cloud onboarding on their own. The `nxCloud: 'skip'` option is now passed for the custom flow to prevent the ID from being generated. E2E tests are updated to verify that `nxCloudId` is undefined in the generated `nx.json` across all workspace presets. ## Related Issue(s) N/A - internal fix for workspace creation behavior. --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> (cherry picked from commit 221ed88)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Current Behavior
When creating a new workspace using
create-nx-workspacewith the "custom" preset flow, annxCloudIdis generated and added tonx.json. This happens even though the onboarding flow is supposed to handle Cloud setup separately via a short URL.Expected Behavior
New workspaces created via
create-nx-workspaceshould not havenxCloudIdset innx.json. Instead, a short URL is provided for users to finish Cloud onboarding on their own. ThenxCloud: 'skip'option is now passed for the custom flow to prevent the ID from being generated.E2E tests are updated to verify that
nxCloudIdis undefined in the generatednx.jsonacross all workspace presets.Related Issue(s)
N/A - internal fix for workspace creation behavior.