Skip to content

Conversation

@PeterSchafer
Copy link
Collaborator

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?

  • This PR cherry picks final changes for the release.
  • It updates the help.
  • It updates the release notes.

Where should the reviewer start?

How should this be manually tested?

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

@snyk-io
Copy link

snyk-io bot commented Oct 7, 2025

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

license/snyk check is complete. No issues have been found. (View Details)

code/snyk check is complete. No issues have been found. (View Details)

@github-actions
Copy link
Contributor

github-actions bot commented Oct 7, 2025

Warnings
⚠️

Please make changes to snyk help text in Gitbook. Changes will be automatically synchronised to Snyk CLI as a scheduled PR.
For more information, see: help/README.md.

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

"Merge pull request #6215 from snyk/docs/automatic-gitbook-update-cli-help-chore/CLI-1187_update_1.1300" is too long. Keep the first line of your commit message under 72 characters.

⚠️

"chore: automatic integration of language server 18cf38d2c11874938203782e53b411affd69efe3" is too long. Keep the first line of your commit message under 72 characters.

⚠️

"chore: automatic integration of language server bfd2a1985fd3d7e4eea2aab8c0a1696c175590fb" is too long. Keep the first line of your commit message under 72 characters.

Generated by 🚫 dangerJS against 6c0ae1d

@PeterSchafer PeterSchafer marked this pull request as ready for review October 7, 2025 15:39
@PeterSchafer PeterSchafer requested review from a team as code owners October 7, 2025 15:39
@PeterSchafer PeterSchafer force-pushed the chore/CLI-1187_update_1.1300 branch from 9b3fb4a to 866f731 Compare October 7, 2025 19:24
@PeterSchafer PeterSchafer enabled auto-merge October 7, 2025 19:24
@PeterSchafer PeterSchafer force-pushed the chore/CLI-1187_update_1.1300 branch 2 times, most recently from 73d9b40 to d797dd9 Compare October 8, 2025 07:46
@PeterSchafer PeterSchafer force-pushed the chore/CLI-1187_update_1.1300 branch from d797dd9 to 83d8cbc Compare October 8, 2025 07:57
team-cli-bot and others added 2 commits October 8, 2025 08:38
…help-chore/CLI-1187_update_1.1300

docs: synchronizing help from snyk/user-docs
@PeterSchafer PeterSchafer merged commit bffd91d into release-candidate Oct 8, 2025
7 checks passed
@PeterSchafer PeterSchafer deleted the chore/CLI-1187_update_1.1300 branch October 8, 2025 09:18
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.

8 participants