@webpieces/rules-config 0.4.470 → 0.4.471
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.471",
|
|
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",
|
|
@@ -9,19 +9,30 @@
|
|
|
9
9
|
# TO ENABLE (client repo):
|
|
10
10
|
# 1. Copy this file to .github/workflows/webpieces-pr-gate.yml and commit it.
|
|
11
11
|
# 2. Set a committed "gateSalt" under the pr-gate section of webpieces.config.json (any non-empty string).
|
|
12
|
-
# 3. In branch-protection for `main`, mark the "webpieces
|
|
13
|
-
#
|
|
12
|
+
# 3. In branch-protection for `main`, mark the "webpieces/pr-gate" COMMIT STATUS required (NOT this
|
|
13
|
+
# workflow's job). wp-finish-upsert-pr posts that status directly on the head sha AFTER editing the
|
|
14
|
+
# PR body, so it is race-free: the push fires `synchronize` before the body edit, and a check that
|
|
15
|
+
# read the body alone would see the previous head's token and flap. The status is attached to the
|
|
16
|
+
# sha and simply does not exist until the gated flow (or this workflow) posts it. (Only a repo admin
|
|
17
|
+
# can set required checks — webpieces cannot do it for you.)
|
|
14
18
|
#
|
|
15
19
|
# NOTE: the salt is committed/obscurity-grade — it stops unhooked teammates, but a determined reader can
|
|
16
20
|
# read it and forge. It is deliberately not cryptographically sound; see RESPONSE-pr-gate-ci-enforcement.
|
|
21
|
+
#
|
|
22
|
+
# CONCURRENCY: do NOT add `concurrency: cancel-in-progress: true` scoped only to the PR — two runs a few
|
|
23
|
+
# seconds apart would let the cancellation policy decide pass/fail. If you scope concurrency, include the
|
|
24
|
+
# event name in the group.
|
|
17
25
|
|
|
18
26
|
name: Webpieces PR Gate
|
|
19
27
|
on:
|
|
20
28
|
pull_request:
|
|
29
|
+
# `edited` matters: it re-runs after wp-finish-upsert-pr rewrites the PR body, a fallback for the
|
|
30
|
+
# push-before-edit ordering. The authoritative signal is the webpieces/pr-gate commit status, though.
|
|
21
31
|
types: [opened, edited, synchronize, reopened]
|
|
22
32
|
permissions:
|
|
23
33
|
contents: read
|
|
24
34
|
pull-requests: read
|
|
35
|
+
statuses: write # wp-check-pr posts the webpieces/pr-gate commit status
|
|
25
36
|
jobs:
|
|
26
37
|
webpieces-pr-gate:
|
|
27
38
|
runs-on: ubuntu-latest
|