@ggdna/dna-gg 1.6.0 → 1.6.1
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/dna/_generated.json
CHANGED
|
@@ -39,7 +39,7 @@
|
|
|
39
39
|
"ecosystem": null,
|
|
40
40
|
"resolvedVersion": null,
|
|
41
41
|
"via": null,
|
|
42
|
-
"hash": "
|
|
42
|
+
"hash": "0x1be177dde62ec3b7"
|
|
43
43
|
}
|
|
44
44
|
],
|
|
45
45
|
"claude": {
|
|
@@ -75,11 +75,11 @@
|
|
|
75
75
|
},
|
|
76
76
|
{
|
|
77
77
|
"path": ".claude/skills/gg-publish/SKILL.md",
|
|
78
|
-
"hash": "
|
|
78
|
+
"hash": "0x7ea44a57ed7d2ae8"
|
|
79
79
|
},
|
|
80
80
|
{
|
|
81
81
|
"path": ".claude/skills/gg-push/SKILL.md",
|
|
82
|
-
"hash": "
|
|
82
|
+
"hash": "0xe9bf8d2d00371cf3"
|
|
83
83
|
},
|
|
84
84
|
{
|
|
85
85
|
"path": ".claude/skills/gg-review/SKILL.md",
|
|
@@ -115,7 +115,7 @@
|
|
|
115
115
|
},
|
|
116
116
|
{
|
|
117
117
|
"path": "doc/guides/for-ai/ai-dev-guide.md",
|
|
118
|
-
"hash": "
|
|
118
|
+
"hash": "0xb3354db9fff082e9"
|
|
119
119
|
},
|
|
120
120
|
{
|
|
121
121
|
"path": "doc/guides/index-guide.md",
|
|
@@ -320,6 +320,12 @@ gg one do commit
|
|
|
320
320
|
gg do push
|
|
321
321
|
```
|
|
322
322
|
|
|
323
|
+
`gg do push` merges the main branches into the feature branches, checks
|
|
324
|
+
and pushes. It upgrades no dependency: new versions, major versions
|
|
325
|
+
included, arrive through the nightly build (`gg do maintain --nightly`).
|
|
326
|
+
Does the ticket need a newer version of a dependency right away? Raise
|
|
327
|
+
its constraint as part of the change, or run `gg do push --upgrade`.
|
|
328
|
+
|
|
323
329
|
## Review
|
|
324
330
|
|
|
325
331
|
Check the diff of every repo of the ticket against its scope first (see
|
|
@@ -369,3 +375,8 @@ terminal must stay outside the ticket — `-i` names the ticket instead.
|
|
|
369
375
|
|
|
370
376
|
gg triggers the pull request merge and publishes the changes to the
|
|
371
377
|
registry. Finally the version tag is created and pushed.
|
|
378
|
+
|
|
379
|
+
A publish resolves the dependencies (`dart pub get`, `<pm> install`) and
|
|
380
|
+
analyzes; it upgrades nothing and does not run the tests again — they
|
|
381
|
+
passed at the commit. Only the constraints on repos the same ticket
|
|
382
|
+
publishes change.
|
|
@@ -7,6 +7,8 @@ description: Prepares the release of a reviewed ticket and hands `gg do publish`
|
|
|
7
7
|
|
|
8
8
|
`gg do publish` merges the pull requests, publishes to the registry and
|
|
9
9
|
creates and pushes the version tags. It is interactive — the user runs it.
|
|
10
|
+
It resolves and analyzes every repo, but upgrades nothing and does not run
|
|
11
|
+
the tests again.
|
|
10
12
|
|
|
11
13
|
## 1. Check the preconditions
|
|
12
14
|
|
|
@@ -15,6 +15,10 @@ gg do push
|
|
|
15
15
|
repos that still carry uncommitted work. If it reports such a repo, run
|
|
16
16
|
`/gg-commit` first and push again.
|
|
17
17
|
|
|
18
|
+
It upgrades no dependency — the nightly build (`gg do maintain --nightly`)
|
|
19
|
+
does. Only when the ticket needs a newer version right away, push with
|
|
20
|
+
`gg do push --upgrade`.
|
|
21
|
+
|
|
18
22
|
## Important
|
|
19
23
|
|
|
20
24
|
- Push only when the user asked for it.
|