feat: add acceptance tests for maven and npm scope [CSENG-122] #6483
Conversation
This file contains hidden or 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
snyk-abedonik
force-pushed
the
feat/add-acceptance-tests-for-scope
branch
from
1e1c258 to
8629320
Compare
snyk-abedonik
changed the title
snyk-abedonik
force-pushed
the
feat/add-acceptance-tests-for-scope
branch
4 times, most recently
from
46b4b8b to
9284be7
Compare
snyk-abedonik
force-pushed
the
feat/add-acceptance-tests-for-scope
branch
from
9284be7 to
d964e9d
Compare
brew42
approved these changes
Jan 30, 2026
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.
Pull Request Submission Checklist
are release-note ready, emphasizing
what was changed, not how.
What does this PR do?
Where should the reviewer start?
How should this be manually tested?
What's the product update that needs to be communicated to CLI users?