add the actual cycle to the build output #293
Open
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.
These PR changes are stricter, adding the actual cycle to the output.
Why are we doing this?
Currently, monorepos are growing, and in our case, jira-frontend, it's over 3000 packages, and the directed graphs are not very helpful without the actual cycle included in the output; most of the engineers will be very confused if they see a graph with 200 nodes as it happened to my coworker lately.