unirepo-cli 0.5.2 → 0.5.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/src/templates.js +14 -1
package/package.json
CHANGED
package/src/templates.js
CHANGED
|
@@ -21,6 +21,12 @@ This repository is a git-subtree monorepo.
|
|
|
21
21
|
|
|
22
22
|
## CLI
|
|
23
23
|
|
|
24
|
+
If \`unirepo\` is not installed, install it first:
|
|
25
|
+
|
|
26
|
+
\`\`\`bash
|
|
27
|
+
npm install -g unirepo-cli
|
|
28
|
+
\`\`\`
|
|
29
|
+
|
|
24
30
|
Preferred when the \`unirepo\` CLI is available:
|
|
25
31
|
|
|
26
32
|
\`\`\`bash
|
|
@@ -67,10 +73,15 @@ git subtree pull --prefix=<subtree> <remote-or-url> <branch> --squash
|
|
|
67
73
|
|
|
68
74
|
3. Make changes inside one or more subtree directories.
|
|
69
75
|
|
|
70
|
-
4. Commit in the monorepo.
|
|
76
|
+
4. Commit in the monorepo. Use one commit per subtree when the changes are independent. When a change is tightly coupled across subtrees (e.g. a shared type change that requires simultaneous updates in both the library and the consumer), commit all affected subtrees together in a single commit so the intent is clear.
|
|
71
77
|
\`\`\`bash
|
|
78
|
+
# Single subtree
|
|
72
79
|
git add <subtree>/
|
|
73
80
|
git commit -m "feat(<subtree>): ..."
|
|
81
|
+
|
|
82
|
+
# Coupled change across subtrees
|
|
83
|
+
git add <subtree-a>/ <subtree-b>/
|
|
84
|
+
git commit -m "feat: ..."
|
|
74
85
|
\`\`\`
|
|
75
86
|
|
|
76
87
|
5. Inspect what changed before pushing.
|
|
@@ -136,4 +147,6 @@ export const GITIGNORE = `.DS_Store
|
|
|
136
147
|
|
|
137
148
|
*.swp
|
|
138
149
|
*.swo
|
|
150
|
+
|
|
151
|
+
AGENTS.md
|
|
139
152
|
`;
|