Skip to content

Conversation

@paulrosca-snyk
Copy link
Contributor

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?

Where should the reviewer start?

How should this be manually tested?

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

@paulrosca-snyk paulrosca-snyk force-pushed the chore/enable-snyk-test-new-workflow-tests branch from 3c44def to 6cd866a Compare November 12, 2025 10:40
@paulrosca-snyk paulrosca-snyk force-pushed the chore/enable-snyk-test-new-workflow-tests branch from 6cd866a to 929aecb Compare November 13, 2025 12:46
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