Skip to content

Conversation

dotkas
Copy link
Contributor

@dotkas dotkas commented Aug 18, 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?

Where should the reviewer start?

How should this be manually tested?

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

Copy link

snyk-io bot commented Aug 18, 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)

@dotkas dotkas force-pushed the dotkas/CLI-792/move-to-private-docker-repo branch 3 times, most recently from 2cdd7d0 to 6cb2484 Compare August 18, 2025 10:21
Copy link
Contributor

github-actions bot commented Aug 18, 2025

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

Generated by 🚫 dangerJS against 7f4df73

@dotkas dotkas force-pushed the dotkas/CLI-792/move-to-private-docker-repo branch from eaba0bf to af35941 Compare August 18, 2025 11:28
@@ -47,22 +47,34 @@ executors:
resource_class: small
docker-amd64:
docker:
- image: snyklabs/cli-build:20250429-091242
- image: snyklabs/cli-build-private:20250818-112438
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not awesome naming, but to not break the pipelines I didn't want to make the existing repository private.

@dotkas dotkas force-pushed the dotkas/CLI-792/move-to-private-docker-repo branch from af35941 to 7f4df73 Compare August 20, 2025 14:07
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.

1 participant