Skip to content

Conversation

@aarlaud
Copy link
Contributor

@aarlaud aarlaud commented Nov 27, 2025

Pull Request Submission Checklist

  • Follows CONTRIBUTING guidelines
  • Commit messages
    are release-note ready, emphasizing
    what was changed, not how.
  • Includes detailed description of changes
  • Contains risk assessment (Low | Medium | High)
  • Highlights breaking API changes (if applicable)
  • Links to automated tests covering new functionality
  • Includes manual testing instructions (if necessary)
  • Updates relevant GitBook documentation (PR link: ___)
  • Includes product update to be announced in the next stable release notes

What does this PR do?

Experimental. Add snyk delta cli extension. WIP.

Where should the reviewer start?

How should this be manually tested?

What's the product update that needs to be communicated to CLI users?

Risk assessment (Low | Medium | High)?

low

Any background context you want to provide?

Drop-in replacement for snyk test if you want only the net new issues in the current scan, compared to latest monitored snapshot(s).

@aarlaud aarlaud force-pushed the feat/add-sca-test-delta-workflow branch from 1712f15 to b8a45e8 Compare November 28, 2025 15:46
@github-actions
Copy link
Contributor

Warnings
⚠️

You've modified files in src/ directory, but haven't updated anything in test folder. Is there something that could be tested?

⚠️ There are multiple commits on your branch, please squash them locally before merging!

Generated by 🚫 dangerJS against b8a45e8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants