-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
switching to an affected strategy #5215
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
Conversation
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 529bc0a. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this branch ✅ Successfully ran 5 targets
Sent with 💌 from NxCloud. |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 529bc0a:
|
|
I don't think the forwarding of |
Co-authored-by: Dominik Dorfmeister <office@dorfmeister.cc>
Yes, something went wrong! lol
|
|
Alright - got the fix now. For the ci workflow, we'll want to make sure to test it. (The issues with the PR workflow were due to this PR coming in from a fork. After checking out with default options, we were in a detatched head state, so Nx was unable to find the main branch in the linked list of commits, so affected command failed. With pushes to main/alpha/etc., this should be a non-issue since we'll always be inside this repo, never a fork. All the same, don't wanna bring things down!) |
What It Does:
nx affectedin addition to the cache--baseoption for nx affected to the PR's target branch--baseoption for nx affected to the commit before the triggering push--baseoption for nx affected to the commit before the triggering push