Skip to content

Conversation

@merrcury
Copy link
Member

What changed? Why was the change needed?

Screenshots

Expand for optional sections

Related enterprise PR

Special notes for your reviewer

@merrcury merrcury merged commit ab5db6b into next Nov 17, 2025
11 of 13 checks passed
@github-actions github-actions bot added the CI/CD label Nov 17, 2025
@merrcury merrcury deleted the feat/all-region branch November 17, 2025 09:03
@github-actions
Copy link
Contributor

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

We require pull request titles to follow specific formatting rules and it looks like your proposed title needs to be adjusted.

Your PR title is: feat(deploy): add support for new production environment 'production-sg-au-uk-jp-kr' in deployment workflow

Requirements:

  1. Follow the Conventional Commits specification
  2. As a team member, include Linear ticket ID at the end: fixes TICKET-ID or include it in your branch name

Expected format: feat(scope): Add fancy new feature fixes NOV-123

Details:
Unknown scope "deploy" found in pull request title "feat(deploy): add support for new production environment 'production-sg-au-uk-jp-kr' in deployment workflow". Scope must match one of: root, api-service, dashboard, inbound-mail, web, webhook, worker, ws, ee-api, ee-auth, ee-billing, ee-dal, ee-shared-services, ee-translation, application-generic, automation, dal, design-system, api, notifications, novui, testing, add-inbox, framework, js, nextjs, novu, providers, react, react-native, shared, stateless, nestjs, nextjs.
PR title must end with 'fixes TICKET-ID' (e.g., 'fixes NOV-123') or include ticket ID in branch name

@netlify
Copy link

netlify bot commented Nov 17, 2025

Deploy Preview for dashboard-v2-novu-staging canceled.

Name Link
🔨 Latest commit 62313fe
🔍 Latest deploy log https://app.netlify.com/projects/dashboard-v2-novu-staging/deploys/691ae4bc0866a5000836018b

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants