[ACS-5107] - improve gha after introducing nx workspace #3420
Conversation
This file contains 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
dominikiwanekhyland
requested review from
DenysVuika and
eromano
as code owners
dominikiwanekhyland
requested review from
nikita-web-ua,
swapnil-verma-gl,
MichalKinas and
AleksanderSklorz
dominikiwanekhyland
changed the title
dominikiwanekhyland
force-pushed
the
ACS-5107-improve-gha-after-introducing-nx-workspace_1
branch
from
b3b9116 to
affdb65
Compare
DenysVuika
approved these changes
Sep 5, 2023
DenysVuika
deleted the
ACS-5107-improve-gha-after-introducing-nx-workspace_1
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x")
What is the current behaviour? (You can also link to an open issue here)
Due to new 'affected' command NX is trying to start tests for content-ce project which has no tests and it's blocking on that step.
What is the new behaviour?
Unit tests are unblocked on CI
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information: