@casomoltd/tooling 0.23.0 → 0.23.2
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/bin/pre-push.sh +10 -8
- package/package.json +1 -1
package/bin/pre-push.sh
CHANGED
|
@@ -4,14 +4,16 @@
|
|
|
4
4
|
PRE_PUSH_REFS=$(cat)
|
|
5
5
|
export PRE_PUSH_REFS
|
|
6
6
|
|
|
7
|
-
# Uniform pre-push for every repo:
|
|
8
|
-
#
|
|
9
|
-
#
|
|
10
|
-
#
|
|
11
|
-
#
|
|
12
|
-
# build
|
|
13
|
-
#
|
|
7
|
+
# Uniform pre-push for every repo: the repo's own health gate, then the
|
|
8
|
+
# release-protocol gates.
|
|
9
|
+
#
|
|
10
|
+
# Building belongs to `check`, not here. A repo whose build fails is not
|
|
11
|
+
# healthy, and any assertion that reads build output (SSR, page meta, sitemap)
|
|
12
|
+
# has to run after the build inside that same script — so `check` is where the
|
|
13
|
+
# step already has to live. Declaring it here as well would give the build two
|
|
14
|
+
# owners and run it twice wherever `check` builds. A repo that needs a build
|
|
15
|
+
# gate adds `npm run build` to its own `check`; one that produces no artifact
|
|
16
|
+
# simply doesn't.
|
|
14
17
|
npm run check \
|
|
15
|
-
&& npm run build \
|
|
16
18
|
&& echo "$PRE_PUSH_REFS" | check-version \
|
|
17
19
|
&& echo "$PRE_PUSH_REFS" | check-tags
|
package/package.json
CHANGED