| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 8 | 0% |
| Section tags | 0 | 2 | 0 | 0% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − Pull Request Rules
- + Infrastructure
Commands
0 shared · 0 only in A · 8 only in B- + docker compose -f docker/local/docker-compose.yml up -d
- + docker compose -f docker/local/docker-compose.agent.yml up -d
- + pnpm start:api:dev
- + pnpm start:worker
- + pnpm start:ws
- + docker compose
- + pnpm build
- + pnpm build:agents
Section tags
0 shared · 2 only in A · 0 only in B- − git-pr
- − do-not
Line diff
novuhq/novu · .cursor/rules/pullrequest.mdc
@@ −1 @@
1---
2description: When creating a new pull request on GitHub, use this to specify the contents
3alwaysApply: false
4---
5
6### Pull Request Rules
7
8**Title format**: `type(scope): Description fixes NOV-<ticket-id>`
9
10- When creating a pull requests from any run, verify that there is a linear ticket associated with the pr (From branch name or other), if not, create the linear ticket before creating the PR and attach the linear ticket id in title (fixes NV-XXX)
11- Examples: `feat(dashboard): add workflow trigger button fixes NOV-123`, `fix(api-service): handle null subscriber case fixes NOV-456`
12
13
14**Scopes**: `dashboard`, `api-service`, `worker`, `shared`, `js`, `react`, `react-native`, `nextjs`, `providers`, `root`, `docs`
15
16**Description**: Summarize what changed and why. List breaking changes. Add screenshots for UI changes. For non-trivial logic or architecture changes, include a concise Mermaid diagram (flow, sequence, or component) so reviewers can grasp the change at a glance.
17
18**Enterprise packages**: When changes touch `enterprise/`, also open a matching PR in `novuhq/packages-enterprise` on a branch from `next`, and cross-link the two PR bodies (monorepo ↔ enterprise). The Validate Submodule Sync test will fail; this is expected when pointing to the `.source` submodule in the novuhq/novu repository. Do not fix it.
19
novuhq/novu · .cursor/rules/infrastructure.mdc
@@ +1 @@
1---
2description: Infrastructure setup, Docker services, and environment configuration
3globs:
4 - "docker/**/*"
5 - "*.env*"
6 - ".env*"
7 - "**/docker-compose*"
8alwaysApply: false
9---
10
11## Infrastructure
12
13**Start all services:** `docker compose -f docker/local/docker-compose.yml up -d`
14
15**Agent environments** use a separate compose file — restart after a reboot with:
16`docker compose -f docker/local/docker-compose.agent.yml up -d`
17
18| Service | Port | Purpose |
19|---------|------|---------|
20| MongoDB | 27017 | Primary database |
21| Redis | 6379 | Caching + Bull queues |
22| ClickHouse | 8123 (HTTP) / 9000 (native) | Analytics, activity feed, traces |
23| LocalStack | 4566 | S3 emulation (optional) |
24
25**Services needed per task:**
26- Dashboard UI only: nothing (user has it running on port 4201)
27- API endpoints: `pnpm start:api:dev`
28- Notification flows: API + `pnpm start:worker`
29- Real-time features: API + Worker + `pnpm start:ws`
30- Full stack: `docker compose` + all of the above
31
32Run `pnpm build` before starting services only if changes were made to `libs/`, `packages/`, or `enterprise/`. Cloud agent install/update uses `pnpm build:agents`, which skips full app builds but still runs `@novu/api-service:build:metadata` (apps otherwise build when their dev servers start).
@@ −1 +1 @@
11 ---
2−description: When creating a new pull request on GitHub, use this to specify the contents
2+description: Infrastructure setup, Docker services, and environment configuration
3+globs:
4+ - "docker/**/*"
5+ - "*.env*"
6+ - ".env*"
7+ - "**/docker-compose*"
38 alwaysApply: false
49 ---
510
6−### Pull Request Rules
11+## Infrastructure
712
8−**Title format**: `type(scope): Description fixes NOV-<ticket-id>`
13+**Start all services:** `docker compose -f docker/local/docker-compose.yml up -d`
914
10−- When creating a pull requests from any run, verify that there is a linear ticket associated with the pr (From branch name or other), if not, create the linear ticket before creating the PR and attach the linear ticket id in title (fixes NV-XXX)
11−- Examples: `feat(dashboard): add workflow trigger button fixes NOV-123`, `fix(api-service): handle null subscriber case fixes NOV-456`
15+**Agent environments** use a separate compose file — restart after a reboot with:
16+`docker compose -f docker/local/docker-compose.agent.yml up -d`
1217
18+| Service | Port | Purpose |
19+|---------|------|---------|
20+| MongoDB | 27017 | Primary database |
21+| Redis | 6379 | Caching + Bull queues |
22+| ClickHouse | 8123 (HTTP) / 9000 (native) | Analytics, activity feed, traces |
23+| LocalStack | 4566 | S3 emulation (optional) |
1324
14−**Scopes**: `dashboard`, `api-service`, `worker`, `shared`, `js`, `react`, `react-native`, `nextjs`, `providers`, `root`, `docs`
25+**Services needed per task:**
26+- Dashboard UI only: nothing (user has it running on port 4201)
27+- API endpoints: `pnpm start:api:dev`
28+- Notification flows: API + `pnpm start:worker`
29+- Real-time features: API + Worker + `pnpm start:ws`
30+- Full stack: `docker compose` + all of the above
1531
16−**Description**: Summarize what changed and why. List breaking changes. Add screenshots for UI changes. For non-trivial logic or architecture changes, include a concise Mermaid diagram (flow, sequence, or component) so reviewers can grasp the change at a glance.
17−
18−**Enterprise packages**: When changes touch `enterprise/`, also open a matching PR in `novuhq/packages-enterprise` on a branch from `next`, and cross-link the two PR bodies (monorepo ↔ enterprise). The Validate Submodule Sync test will fail; this is expected when pointing to the `.source` submodule in the novuhq/novu repository. Do not fix it.
19−
32+Run `pnpm build` before starting services only if changes were made to `libs/`, `packages/`, or `enterprise/`. Cloud agent install/update uses `pnpm build:agents`, which skips full app builds but still runs `@novu/api-service:build:metadata` (apps otherwise build when their dev servers start).
