@webpieces/rules-config 0.4.418 → 0.4.419
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
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@webpieces/rules-config",
|
|
3
|
-
"version": "0.4.
|
|
3
|
+
"version": "0.4.419",
|
|
4
4
|
"description": "Shared webpieces.config.json loader. Single source of truth for validation rule configuration consumed by @webpieces/ai-hook-rules, @webpieces/code-rules, and @webpieces/nx-webpieces-rules.",
|
|
5
5
|
"type": "commonjs",
|
|
6
6
|
"main": "./src/index.js",
|
|
@@ -3,6 +3,27 @@
|
|
|
3
3
|
Generated by `@webpieces/pr-gate` (refreshed on every `wp-*` PR/merge command, so it can't drift).
|
|
4
4
|
Read this before running any `wp-start-update` / `wp-start-upsert-pr` / `wp-finish-upsert-pr`.
|
|
5
5
|
|
|
6
|
+
## ⛔ START HERE — finishing a feature MEANS posting the PR
|
|
7
|
+
|
|
8
|
+
**A feature is NOT done when the build is green. It is done when the PR is up.** A green
|
|
9
|
+
`build-all` / passing tests is the *middle* of the job, not the end — the AI runs `build-all` many
|
|
10
|
+
times while developing, and none of those greens mean "ready to review."
|
|
11
|
+
|
|
12
|
+
When you believe the work is complete — code written, tests passing, `build-all` green — your **very
|
|
13
|
+
next action is to post the PR**, not to stop and ask. Do NOT end your turn with "want me to open a PR?"
|
|
14
|
+
That question is already answered: **yes, always.** Run the flow:
|
|
15
|
+
|
|
16
|
+
```bash
|
|
17
|
+
pnpm wp-start-upsert-pr # updates from main, pushes, runs the build gate, tells you to write review.json
|
|
18
|
+
# → write .webpieces/review.json (its `title` becomes the PR title)
|
|
19
|
+
pnpm wp-finish-upsert-pr # authoritative build gate, then creates/updates the PR
|
|
20
|
+
```
|
|
21
|
+
|
|
22
|
+
The tooling never commits for you (see the golden rule below), so **commit your work first**, then run
|
|
23
|
+
`wp-start-upsert-pr`. The only reasons to stop *before* posting are: the human explicitly said "don't
|
|
24
|
+
open a PR yet," or the build/tests are red. Otherwise, finishing the feature and posting the PR are the
|
|
25
|
+
same step — do not treat them as separate, opt-in actions.
|
|
26
|
+
|
|
6
27
|
## Golden rule: the tooling NEVER commits your work for you
|
|
7
28
|
|
|
8
29
|
Before running any `wp-*` PR/merge command, your working tree must be 100% clean:
|