@jphutchins/code-review 0.1.0-alpha.63 → 0.1.0-alpha.65
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/README.md +3 -3
- package/dist/index.js +635 -486
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
- package/schema/VERSIONING.md +2 -1
- package/schema/findings.schema.json +9 -1
- package/templates/comment.eta +13 -1
- package/templates/inline.eta +5 -1
package/README.md
CHANGED
|
@@ -38,7 +38,7 @@ npx @jphutchins/code-review <subcommand>
|
|
|
38
38
|
| Subcommand | What it does |
|
|
39
39
|
| --- | --- |
|
|
40
40
|
| `post` | Post a complete review from findings + envelope + diff — the one-call path. The findings are listed in the sticky summary; `--inline` renders the in-diff ones as comments on the diff instead. Also renders the review into `$GITHUB_STEP_SUMMARY`: the sticky is overwritten each round, the run summary keeps each round as it stood |
|
|
41
|
-
| `gather` | Resolve the PR from the CI head SHA and gather the review inputs (diff with git-diff fallback, PR context, prior bot review, the
|
|
41
|
+
| `gather` | Resolve the PR from the CI head SHA and gather the review inputs (diff with git-diff fallback, PR context, prior bot review, the implementer's answers (`Review-Response:` lines and verdict tables), failing-job logs) into the directory named by `--out-dir` (default: the current directory; the shipped workflows use `$RUNNER_TEMP/gather`) |
|
|
42
42
|
| `parse-command` | Resolve a PR's head from its number and parse a ChatOps trigger comment (`/code-review [24m] [$1.00] <instructions>`) into review overrides — the on-demand comment trigger |
|
|
43
43
|
| `react` | Add/remove a GitHub comment reaction — the ChatOps acknowledgement (👀 on receipt, 🚀 on completion) |
|
|
44
44
|
| `await-ci` | Wait for a PR head's CI run to conclude and emit its real conclusion + run id — so an on-demand comment review routes on the CI result (success → full, failure → mechanic) instead of reviewing blind |
|
|
@@ -107,7 +107,7 @@ links to:
|
|
|
107
107
|
[`src/surface.ts`](src/surface.ts).
|
|
108
108
|
|
|
109
109
|
The embedded document is the agent's **complete** findings document — the same `schema_version`
|
|
110
|
-
0.
|
|
110
|
+
0.11.0 contract the review agent is held to and
|
|
111
111
|
[`schema/findings.schema.json`](schema/findings.schema.json) validates, and the same object the
|
|
112
112
|
comment is rendered from. The agent's fields are embedded verbatim; the pipeline stamps one field the
|
|
113
113
|
agent never writes — `convergence` (below) — so the whole review, findings and convergence signal
|
|
@@ -115,7 +115,7 @@ links to:
|
|
|
115
115
|
|
|
116
116
|
```json
|
|
117
117
|
{
|
|
118
|
-
"schema_version": "0.
|
|
118
|
+
"schema_version": "0.11.0",
|
|
119
119
|
"verdict": "comment",
|
|
120
120
|
"summary": "...",
|
|
121
121
|
"findings": [],
|