unkeyed / unkey

Open source API management platform
https://go.unkey.com
Other
2.9k stars 286 forks source link

wip #1836

Closed chronark closed 3 months ago

chronark commented 3 months ago

Huly®: ENG-1830

vercel[bot] commented 3 months ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
dashboard ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 1, 2024 3:30pm
planetfall ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 1, 2024 3:30pm
play ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 1, 2024 3:30pm
workflows ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 1, 2024 3:30pm
www ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 1, 2024 3:30pm
changeset-bot[bot] commented 3 months ago

⚠️ No Changeset found

Latest commit: d384b07456d402589cbd6d9cb09f62b7ce659b3d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

github-actions[bot] commented 3 months ago

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted. Here is an example:

<type>[optional scope]: <description>
fix: I fixed something for Unkey

Details:

No release type found in pull request title "wip". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit