The four CI badges at the top of the README point at workflow files by path. Three of those paths no longer exist, so the badges render as "no status" rather than a build result.
Fetching each badge shows it directly:
| Badge in the README |
Workflow path |
Renders as |
| rspec |
rspec.yml |
rspec - no status |
| frontend |
frontend.yml |
frontend - failing |
| ERB lint |
erb_lint.yml |
ERB lint - no status |
| standardrb lint |
ruby_lint.yml |
standardrb lint - no status |
The three dead ones were removed in #520 (1fd910f2, 2021-10-14), "Combines backend CI jobs into single workflow", which replaced them with backend.yml. The badges were not updated at the time. The workflows in the repo today are backend.yml, frontend.yml and native.yml.
Why this is not a straight rename
Badges are per workflow, not per job. rspec, erb-lint and standardrb are now three jobs inside backend.yml, so there is no URL that reports them individually — one backend badge covers all of them. native.yml has never had a badge at all.
So the four badges become three:
[](https://github.com/rubyforgood/Flaredown/actions/workflows/backend.yml)
[](https://github.com/rubyforgood/Flaredown/actions/workflows/frontend.yml)
[](https://github.com/rubyforgood/Flaredown/actions/workflows/native.yml)
Both backend.yml and native.yml currently report passing on master, so this would replace three blank badges with two accurate green ones.
Separately: the frontend build is red
Worth flagging because it is the one badge that does work. frontend.yml has been failing on master since 2026-07-21, from the merge of #847 ("docker-dev-modernization"). The run before it, on 2026-07-12, passed. That looks like a real regression rather than a badge problem, and probably wants its own issue — noting it here only because fixing the badges will stop hiding it behind three blank ones.
Found while checking whether #870 (the Ruby 3.4 / Rails 8.1 upgrade) needed README changes. It does not touch any of this, hence a separate issue.
The four CI badges at the top of the README point at workflow files by path. Three of those paths no longer exist, so the badges render as "no status" rather than a build result.
Fetching each badge shows it directly:
rspec.ymlrspec - no statusfrontend.ymlfrontend - failingerb_lint.ymlERB lint - no statusruby_lint.ymlstandardrb lint - no statusThe three dead ones were removed in #520 (
1fd910f2, 2021-10-14), "Combines backend CI jobs into single workflow", which replaced them withbackend.yml. The badges were not updated at the time. The workflows in the repo today arebackend.yml,frontend.ymlandnative.yml.Why this is not a straight rename
Badges are per workflow, not per job.
rspec,erb-lintandstandardrbare now three jobs insidebackend.yml, so there is no URL that reports them individually — onebackendbadge covers all of them.native.ymlhas never had a badge at all.So the four badges become three:
Both
backend.ymlandnative.ymlcurrently reportpassingonmaster, so this would replace three blank badges with two accurate green ones.Separately: the frontend build is red
Worth flagging because it is the one badge that does work.
frontend.ymlhas been failing onmastersince 2026-07-21, from the merge of #847 ("docker-dev-modernization"). The run before it, on 2026-07-12, passed. That looks like a real regression rather than a badge problem, and probably wants its own issue — noting it here only because fixing the badges will stop hiding it behind three blank ones.Found while checking whether #870 (the Ruby 3.4 / Rails 8.1 upgrade) needed README changes. It does not touch any of this, hence a separate issue.