@cratis/pi 7.87.0 → 7.87.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.
|
@@ -72,7 +72,11 @@ paths:
|
|
|
72
72
|
- A bot's pre-push verification build must match the strictest configuration any CI in
|
|
73
73
|
the organization applies to the same commit (build `Release` when consumers enforce
|
|
74
74
|
analyzers there). Do not add `[skip ci]` to bot commits as a load optimization: the
|
|
75
|
-
downstream CI run is the only check that sees the merged result.
|
|
75
|
+
downstream CI run is the only check that sees the merged result. One exception: a
|
|
76
|
+
bootstrap commit that changes **only** bootstrapped wrapper workflow files, whose
|
|
77
|
+
content the source repository's CI verified before the rollout, may carry
|
|
78
|
+
`[skip ci]` once the same wrapper content has landed with CI running in one canary
|
|
79
|
+
repository. Package-update bots, and any commit touching another file, keep normal CI.
|
|
76
80
|
- Comment-triggered agent workflows must gate on the trigger phrase in the job's `if:`
|
|
77
81
|
(for example `contains(github.event.comment.body, '@claude')`) so a runner only
|
|
78
82
|
starts when the agent is actually addressed.
|
|
@@ -71,7 +71,11 @@ paths:
|
|
|
71
71
|
- A bot's pre-push verification build must match the strictest configuration any CI in
|
|
72
72
|
the organization applies to the same commit (build `Release` when consumers enforce
|
|
73
73
|
analyzers there). Do not add `[skip ci]` to bot commits as a load optimization: the
|
|
74
|
-
downstream CI run is the only check that sees the merged result.
|
|
74
|
+
downstream CI run is the only check that sees the merged result. One exception: a
|
|
75
|
+
bootstrap commit that changes **only** bootstrapped wrapper workflow files, whose
|
|
76
|
+
content the source repository's CI verified before the rollout, may carry
|
|
77
|
+
`[skip ci]` once the same wrapper content has landed with CI running in one canary
|
|
78
|
+
repository. Package-update bots, and any commit touching another file, keep normal CI.
|
|
75
79
|
- Comment-triggered agent workflows must gate on the trigger phrase in the job's `if:`
|
|
76
80
|
(for example `contains(github.event.comment.body, '@claude')`) so a runner only
|
|
77
81
|
starts when the agent is actually addressed.
|