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

npx nx show projects --affected - Show which files/why it's being triggered #23149

Closed
2 of 4 tasks
broksonic21 opened this issue May 2, 2024 · 2 comments
Closed
2 of 4 tasks

Comments

@broksonic21
Copy link

Documentation issue

  • Reporting a typo
  • Reporting a documentation bug
  • Documentation improvement
  • Documentation feedback

Is there a specific documentation page you are reporting?

I can't find documentation on a flag to send to npx nx show projects --affected in order to see why nx thinks the project was affected. would love a list of files or an explanation on what's flagging each of them. --verbose doesn't return any extra info.

Additional context or description

Trying to track down why it's reporting too many projects beyond what we'd expect

@AgentEnder
Copy link
Member

There's not currently a flag or capability to explain why a project has been marked as affected. We may consider doing something along these lines in the future, but as of now its not present. For now, I'm going to close this out. Stay tuned though, the capability may come in the future.

Copy link

github-actions bot commented Jun 3, 2024

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants