bleedingdeacons / reconcile / 31013218518
91%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 25
Run time 1min
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
coverage: 91.415%. Remained the same
31013218518

push

github

web-flow 
chore(tooling): make PSR-12 a gate and badge the standard (#39)

PHPCS has been running advisory since it was added, with a note to promote
it once the repo was green. It never was, but every finding turned out to be
either a WordPress requirement, a test-only idiom, or whitespace phpcbf
fixes on its own.

Exclude the first two groups in .phpcs.xml.dist, each with the reason:

- Generic.Files.LineEndings — git normalises to LF in the index, so this
  only ever fired on Windows working copies, never in CI.
- Generic.Files.LineLength — PSR-12's 120-char limit, against markup and
  option literals where wrapping reads worse.
- PSR1.Files.SideEffects — the mandatory `if (!defined('ABSPATH')) exit;`
  guard counts as a side effect next to the class declaration.
- PSR1.Methods.CamelCapsMethodName, PSR1.Classes.ClassDeclaration,
  Squiz.Classes.ValidClassName, PSR12.Files.FileHeader — scoped to tests/,
  where snake_case BDD names and global WP_* stubs are deliberate.

phpcbf then handled the rest: opening braces onto their own line, inline
control structures expanded, multi-line call arguments reindented, trailing
blank lines before closing braces dropped. No behaviour changes.

With that the repo is clean, so PHPCS moves out of the advisory block and
becomes a gate.

The README badge reads the standard out of .phpcs.xml.dist via shields'
dynamic/xml rather than hardcoding it, matching what the PHPStan badge does
with phpstan.neon.dist. A CI step asserts the XPath still resolves, the same
guard the PHPStan badge already has.

2364 of 2586 relevant lines covered (91.42%)

7.48 hits per line

Jobs
ID Job ID Ran Files Coverage
1 31013218518.1 25
91.42
GitHub Action Run
Source Files on build 31013218518