fix(ci): a workflow TEMPLATE was living in .github/workflows/, so GitHub ran it - #222
Merged
Merged
Conversation
…Hub ran it
example-bashrs.yml says "Copy this to your repo's .github/workflows/ directory"
in its own header. It was already IN .github/workflows/, so GitHub executed it
on every push touching `**/*.sh` or `**/Makefile`.
It cannot pass here, by construction:
- `files: scripts/deploy.sh` — does not exist in this repo (it is the
placeholder path the reader is meant to replace)
- `args: '--tier production'` — `bashrs gate --tier` is a u8 (1=fast,
2=pre-commit, 3=nightly), so clap rejects it:
"invalid value 'production' for '--tier <TIER>': invalid digit found in
string"
Five jobs — Lint Shell Scripts, Lint (SARIF), Quality Score, Property Testing,
Quality Gate — have therefore been red on every matching push since v6.66.0
(2026-04-08), four months. They fired on an unrelated Makefile edit, which is
how this was found.
Moved to docs/examples/github-action-workflow.yml, where it is documentation
instead of a running job, and corrected so anyone copying it does not inherit
the invalid tier. The header now explains why it lives outside
.github/workflows/, so it does not get "helpfully" moved back.
Five permanently-red checks on unrelated PRs is not a minor annoyance: it is
what teaches a team that red is normal. Same reason the bashrs lint step was
deleted from a downstream repo in #209.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This was referenced Aug 11, 2026
fix(oracle): point the extracted test module at the crate root, and test the workspace (GH-214)
#223
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
example-bashrs.ymlsays "Copy this to your repo's .github/workflows/ directory" in its own header. It was already in.github/workflows/, so GitHub executed it on every push touching**/*.shor**/Makefile.It cannot pass here, by construction:
files: scripts/deploy.sh— doesn't exist in this repo. It's the placeholder path the reader is meant to replace.args: '--tier production'—bashrs gate --tieris au8(1=fast, 2=pre-commit, 3=nightly), so clap rejects it outright:Five jobs — Lint Shell Scripts, Lint (SARIF), Quality Score, Property Testing, Quality Gate — have been red on every matching push since v6.66.0 (2026-04-08). Four months.
I found it because it fired on an unrelated
Makefileedit in #221.Fix
Moved to
docs/examples/github-action-workflow.yml, where it's documentation rather than a running job, and corrected the invalid tier so anyone copying it doesn't inherit the bug. The header now explains why it lives outside.github/workflows/, so it doesn't get helpfully moved back.Why this is worth a PR rather than a shrug
Five permanently-red checks on unrelated PRs isn't a minor annoyance — it's what teaches a team that red is normal. It's the same mechanism that got the
bashrs lintstep deleted from a downstream repo in #209: a check that can't be satisfied doesn't get fixed, it gets ignored, and then it gets removed.🤖 Generated with Claude Code