@ggdna/dna-gg 1.1.1 → 1.3.0

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.
@@ -39,7 +39,7 @@
39
39
  "ecosystem": null,
40
40
  "resolvedVersion": null,
41
41
  "via": null,
42
- "hash": "0xa4329d4ad27ccd8a"
42
+ "hash": "0x7e5e4bbb754c4f13"
43
43
  }
44
44
  ],
45
45
  "claude": {
@@ -83,7 +83,7 @@
83
83
  },
84
84
  {
85
85
  "path": ".claude/skills/gg-review/SKILL.md",
86
- "hash": "0x8583deb0630bba47"
86
+ "hash": "0x55b2f0deb18d70d4"
87
87
  },
88
88
  {
89
89
  "path": ".claude/skills/gg-ticket/SKILL.md",
@@ -115,7 +115,7 @@
115
115
  },
116
116
  {
117
117
  "path": "doc/guides/for-ai/ai-dev-guide.md",
118
- "hash": "0x5ac430cba252b5bc"
118
+ "hash": "0xb6eecdb4c7a1ebe8"
119
119
  },
120
120
  {
121
121
  "path": "doc/guides/index-guide.md",
@@ -169,7 +169,9 @@ ticket.
169
169
  [Describe every repo in its own terms](#describe-every-repo-in-its-own-terms)).
170
170
  Keep every repo in its scope while you code: stop and propose a split,
171
171
  a new repo or a move as soon as code does not fit (see
172
- [Keep every repo in its scope](#keep-every-repo-in-its-scope))
172
+ [Keep every repo in its scope](#keep-every-repo-in-its-scope)).
173
+ Before each change, if the repo has `doc/guides/architecture-guide.md`,
174
+ decide where the code goes as its `@placement` describes
173
175
  - Plan only: skip this step. The following steps then apply to the project
174
176
  management repo only.
175
177
 
@@ -319,7 +321,8 @@ gg do review
319
321
  ```
320
322
 
321
323
  gg creates pull requests for each repo and prints the URLs to the
322
- terminal.
324
+ terminal. Print every URL to the user, one line per repo, and open each
325
+ pull request without auto-merge in the browser.
323
326
 
324
327
  Afterwards load the review-light skill and execute it.
325
328
 
@@ -51,15 +51,27 @@ gg do review
51
51
  ```
52
52
 
53
53
  gg creates a pull request for each repo and prints the URLs to the
54
- terminal.
54
+ terminal, below `Please open and review:`. The user does not see that
55
+ output, so pass the URLs on:
56
+
57
+ - Print every URL to the user, one line per repo: `<repo>: <url>`. Name
58
+ each repo that gg reports as `No pull request for <repo>`, with the
59
+ reason
60
+ - Open every pull request without auto-merge in the browser. Ask the
61
+ provider whether auto-merge is set:
62
+ - GitHub: `gh pr view <url> --json autoMergeRequest` — `null` means off
63
+ - Azure DevOps: `az repos pr show --id <id> --query autoCompleteSetBy`
64
+ — empty means off
65
+ - Open the URL with `start "" "<url>"` on Windows, `open "<url>"` on
66
+ macOS and `xdg-open "<url>"` on Linux
55
67
 
56
68
  ## 4. Review the changes
57
69
 
58
70
  Load the `/review-light` skill and execute it.
59
71
 
60
72
  A fix goes through `/gg-commit` and `/gg-push`, then run `gg do review`
61
- again. Update the blog post of the repo when the fix changes what it
62
- describes.
73
+ again. Print and open its pull request URLs as in step 3. Update the blog
74
+ post of the repo when the fix changes what it describes.
63
75
 
64
76
  ## Important
65
77
 
@@ -67,3 +79,4 @@ describes.
67
79
  - Never write a blog post in a repo the ticket did not change, apart from
68
80
  the project management repo.
69
81
  - Never start `gg do review` without the user's confirmation.
82
+ - Always print the pull request URLs after `gg do review`.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ggdna/dna-gg",
3
- "version": "1.1.1",
3
+ "version": "1.3.0",
4
4
  "description": "DNA layer: gg CLI workflow guides, repo setup scripts and CI check",
5
5
  "keywords": [
6
6
  "dna",