| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 0 | 2 | 0% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − Dependency Graph
- + Pull Request Rules
Commands
neither file has anySection tags
0 shared · 0 only in A · 2 only in B- + git-pr
- + do-not
Line diff
novuhq/novu · .cursor/rules/dependency-graph.mdc
@@ −1 @@
1---
2description: Novu monorepo dependency graph — use when assessing blast radius before changing shared code
3globs:
4alwaysApply: false
5---
6
7## Dependency Graph
8
9```mermaid
10graph TD
11 subgraph apps [Apps]
12 api[api]
13 dashboard[dashboard]
14 worker[worker]
15 ws[ws]
16 end
17 subgraph libs [Libs - internal only]
18 dal[dal]
19 appGeneric[application-generic]
20 end
21 subgraph pkgs [Packages - published to NPM]
22 shared[shared]
23 framework[framework]
24 jsSDK[js]
25 reactSDK[react]
26 end
27 api --> appGeneric --> dal
28 worker --> appGeneric
29 ws --> appGeneric
30 api --> shared
31 worker --> shared
32 dashboard --> reactSDK --> jsSDK --> shared
33 dashboard --> framework
34```
35
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
@@ −1 +1 @@
11 ---
2−description: Novu monorepo dependency graph — use when assessing blast radius before changing shared code
3−globs:
2+description: When creating a new pull request on GitHub, use this to specify the contents
43 alwaysApply: false
54 ---
65
7−## Dependency Graph
6+### Pull Request Rules
87
9−```mermaid
10−graph TD
11− subgraph apps [Apps]
12− api[api]
13− dashboard[dashboard]
14− worker[worker]
15− ws[ws]
16− end
17− subgraph libs [Libs - internal only]
18− dal[dal]
19− appGeneric[application-generic]
20− end
21− subgraph pkgs [Packages - published to NPM]
22− shared[shared]
23− framework[framework]
24− jsSDK[js]
25− reactSDK[react]
26− end
27− api --> appGeneric --> dal
28− worker --> appGeneric
29− ws --> appGeneric
30− api --> shared
31− worker --> shared
32− dashboard --> reactSDK --> jsSDK --> shared
33− dashboard --> framework
34−```
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.
3519
