@biffo/cli 0.190.1 → 0.191.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.
@@ -215,8 +215,15 @@ pytest_is_fast() {
215
215
  #
216
216
  # With no ci.yml there is nothing to mirror, so everything applicable runs:
217
217
  # best-effort beats silence in a repo that has no pipeline to disagree with.
218
+ # NO_CI is set once, up front, so the two states this predicate conflates stay
219
+ # distinguishable to the reader even though it answers the same for both (#942).
220
+ # "Yes, CI runs this" and "there is no CI to ask" are not the same claim, and a
221
+ # repo that LOST its ci.yml must not read as maximally covered. The summary
222
+ # below says which one produced the run.
223
+ [ -f .github/workflows/ci.yml ] || NO_CI=1
224
+
218
225
  ci_has() {
219
- [ -f .github/workflows/ci.yml ] || return 0
226
+ [ -n "${NO_CI:-}" ] && return 0
220
227
  grep -qE "$1" .github/workflows/ci.yml
221
228
  }
222
229
 
@@ -533,4 +540,7 @@ if [ -z "$PASSED" ]; then
533
540
  fi
534
541
  printf '\033[32mverify passed\033[0m -%s\n' "$PASSED"
535
542
  [ -n "$SKIPPED" ] && printf '\033[90mnot applicable here:%s\033[0m\n' "$SKIPPED"
543
+ # Say which question was answered. Without this, a repo whose ci.yml was deleted
544
+ # prints exactly what a fully-mirrored repo prints (#942).
545
+ [ -n "${NO_CI:-}" ] && printf '\033[33mno ci.yml - nothing to mirror, so every applicable check ran as\nbest-effort. This is NOT evidence that CI requires them. If this repo is\nmeant to have CI, its workflow is missing.\033[0m\n'
536
546
  printf '\n'
@@ -215,8 +215,15 @@ pytest_is_fast() {
215
215
  #
216
216
  # With no ci.yml there is nothing to mirror, so everything applicable runs:
217
217
  # best-effort beats silence in a repo that has no pipeline to disagree with.
218
+ # NO_CI is set once, up front, so the two states this predicate conflates stay
219
+ # distinguishable to the reader even though it answers the same for both (#942).
220
+ # "Yes, CI runs this" and "there is no CI to ask" are not the same claim, and a
221
+ # repo that LOST its ci.yml must not read as maximally covered. The summary
222
+ # below says which one produced the run.
223
+ [ -f .github/workflows/ci.yml ] || NO_CI=1
224
+
218
225
  ci_has() {
219
- [ -f .github/workflows/ci.yml ] || return 0
226
+ [ -n "${NO_CI:-}" ] && return 0
220
227
  grep -qE "$1" .github/workflows/ci.yml
221
228
  }
222
229
 
@@ -533,4 +540,7 @@ if [ -z "$PASSED" ]; then
533
540
  fi
534
541
  printf '\033[32mverify passed\033[0m -%s\n' "$PASSED"
535
542
  [ -n "$SKIPPED" ] && printf '\033[90mnot applicable here:%s\033[0m\n' "$SKIPPED"
543
+ # Say which question was answered. Without this, a repo whose ci.yml was deleted
544
+ # prints exactly what a fully-mirrored repo prints (#942).
545
+ [ -n "${NO_CI:-}" ] && printf '\033[33mno ci.yml - nothing to mirror, so every applicable check ran as\nbest-effort. This is NOT evidence that CI requires them. If this repo is\nmeant to have CI, its workflow is missing.\033[0m\n'
536
546
  printf '\n'
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@biffo/cli",
3
- "version": "0.190.1",
3
+ "version": "0.191.1",
4
4
  "description": "Biffo project scaffolding CLI",
5
5
  "license": "MIT",
6
6
  "type": "module",