• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

MushroomObserver / mushroom-observer / 26460075072
96%

Build:
DEFAULT BRANCH: main
Ran 26 May 2026 04:10PM UTC
Jobs 1
Files 1009
Run time 3min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

26 May 2026 04:06PM UTC coverage: 96.419%. Remained the same
26460075072

push

github

web-flow
Lock in two .claude/rules: PR bodies via --body-file + Phlex-conversion placement (#4367)

* Add .claude/rules/gh_pr_bodies.md: write PR bodies to a file

When opening or editing a GitHub PR with `gh pr create` /
`gh pr edit`, the body should always come from a file via
`--body-file`. HEREDOC bodies (`$(cat <<'EOF' ... EOF)`) mangle
backticks: shell escapes them to `\` + backtick, the GitHub API
passes the literal through, and Markdown renders the backslash as a
visible character before the tick — so `Foo::Bar` ships as
`\Foo::Bar\`, losing the monospace treatment.

I've shipped a few PRs with that drift; the user has flagged it
enough times that it's now a permanent project-level rule rather
than a "remember next time" thing.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* phlex_conversions: clarify ERB-views default + UI-primitive exception

Two precise points the previous wording elided:

1. ERB files under `app/views/` get converted to Phlex classes under
   `app/views/controllers/`, not `app/components/`. The rule is about
   the source location — anything that lived as ERB under views/ is
   by definition controller-specific content. Applies to tables,
   sidebars, panels, navs, modals, page wrappers, list rows, not
   just forms.

2. Carve-out for true UI primitives. If during a conversion you
   extract a genuine reusable building block — button group, badge,
   alert, etc. — that piece can go to `app/components/` even with no
   concrete second caller, because it's recognizably-generic UI. The
   speculative-future-caller carve-out applies *only* to such
   primitives, not to page-specific fragments that happen to look
   like components on the surface.

Adds the "would a stranger call this a component?" heuristic for
deciding between the two homes when the case is fuzzy.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

38992 of 40440 relevant lines covered (96.42%)

667.51 hits per line

Jobs
ID Job ID Ran Files Coverage
1 26460075072.1 26 May 2026 04:10PM UTC 1009
96.42
GitHub Action Run
Source Files on build 26460075072
  • Tree
  • List 1009
  • Changed 9
  • Source Changed 9
  • Coverage Changed 3
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #26460075072
  • e54a15a0 on github
  • Prev Build on main (#26459747281)
  • Next Build on main (#26460061360)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc