Some checks failed
CI / action-exercise (pull_request) Successful in 29s
CI / self-guards (pull_request) Failing after 32s
CI / release-exercise (pull_request) Successful in 39s
CI / docs-sync-exercise (pull_request) Successful in 12s
labels / labels (pull_request) Successful in 14s
Refs guard / refs-not-closing (pull_request) Successful in 11s
CI / test (pull_request) Failing after 1m11s
25 lines
1.1 KiB
Bash
Executable file
25 lines
1.1 KiB
Bash
Executable file
#!/usr/bin/env bash
|
|
# The release doors' executable path (discussion #217; issue #237). The
|
|
# 0.5.0 record had to explain why lib/ruling.sh changed without changing a
|
|
# door. Keep this list executable so a doors-unchanged record measures the
|
|
# workflow and only the scripts it actually runs, while the test catches a
|
|
# new or removed dependency before a record can silently omit it.
|
|
#
|
|
# On this tree the doors also speak the forge shim: #191 ported lib/facts.sh
|
|
# and release.yml off `gh` so a Forgejo consumer can publish at all, which
|
|
# makes lib/forge.sh part of the doors' executable path here. The backends it
|
|
# loads (lib/forge-github.sh, lib/forge-forgejo.sh) are sourced through
|
|
# $FORGE_LIB_DIR at run time rather than by a literal `.` line, so the
|
|
# transitive scan cannot see them and listing them would read as a stale
|
|
# path; lib/forge.sh standing for the trio is the honest entry (#198).
|
|
set -euo pipefail
|
|
|
|
printf '%s\n' \
|
|
.github/workflows/release.yml \
|
|
bin/ \
|
|
lib/version.sh \
|
|
lib/decide.sh \
|
|
lib/preflight.sh \
|
|
lib/facts.sh \
|
|
lib/changelog.sh \
|
|
lib/forge.sh
|