-
-
Notifications
You must be signed in to change notification settings - Fork 204
chore: migrate to standalone project config #977
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
chore: migrate to standalone project config #977
Conversation
@edbzn I think there's something wrong with the CI. I forked this repo and made the branch there and created a PR from my forked repo's branch to this repo. The usual way. |
Like this PR #678 , the check fails: https://github.com/rx-angular/rx-angular/pull/678/checks?check_run_id=3400464026 |
I think this one
I think this one should use |
Moved the CI issue discussion to #979 |
Nx Cloud ReportCI ran the following commands for commit 4d1b9d6. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this branch
Sent with 💌 from NxCloud. |
@hoebbelsB merged latest |
Hi @edbzn! can we add |
Description
Closes #971
This PR addresses the goal to move to per project configuration introduced in Nx 12.5. It uses the command mentioned in the issue.
PR #974 got closed when tried to rename the branch via GitHub web UI 🤷♂️