Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove v1 from next #7742

Draft
wants to merge 3 commits into
base: next
Choose a base branch
from
Draft

Remove v1 from next #7742

wants to merge 3 commits into from

Conversation

SokratisVidros
Copy link
Contributor

What changed? Why was the change needed?

Screenshots

Expand for optional sections

Related enterprise PR

Special notes for your reviewer

The legacy code for the web Dashboard will live in a v1 branch from now on. The reason for this removal is to declutter the monorepo, reduce the NPM dependencies and speed up the CICD.
Copy link

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.

Your PR title is: Remove v1 from next
It should be something like: feat(scope): Add fancy new feature

Details:

No release type found in pull request title "Remove v1 from next". 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

Copy link

netlify bot commented Feb 17, 2025

Deploy Preview for dev-web-novu failed. Why did it fail? →

Name Link
🔨 Latest commit 0f28bdd
🔍 Latest deploy log https://app.netlify.com/sites/dev-web-novu/deploys/67b373f76943c50008905fb5

Copy link

netlify bot commented Feb 17, 2025

Deploy Preview for dashboard-v2-novu-staging ready!

Name Link
🔨 Latest commit 0f28bdd
🔍 Latest deploy log https://app.netlify.com/sites/dashboard-v2-novu-staging/deploys/67b373f78be7000008d53104
😎 Deploy Preview https://deploy-preview-7742.dashboard-v2.novu-staging.co
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

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

Successfully merging this pull request may close these issues.

1 participant