Skip to content

issues-37 | Add Pint linter snippet - #38

Open
prog-time wants to merge 3 commits into
mainfrom
issues-37
Open

issues-37 | Add Pint linter snippet#38
prog-time wants to merge 3 commits into
mainfrom
issues-37

Conversation

@prog-time

Copy link
Copy Markdown
Owner

Summary

Adds a pint snippet to the linters category — Laravel/PHP code-style check via vendor/bin/pint --test.

The catalog ships phpcs, but the de-facto standard in Laravel projects is Laravel Pint (PHP-CS-Fixer wrapper, PSR-12 + Laravel preset). Direct sibling of rubocop/ruff. Pint needs no mandatory config (pint.json is optional), so the script guards on the binary, not a config file.

Changes (standard snippet convention)

  • scripts/shell/linters/pint.shset -euo pipefail; resolves vendor/bin/pint or pint on PATH, else ::error::; runs pint --test (check-only, no auto-fix).
  • tests/linters/pint.bats — covers: pint not installed, clean code, style issues.
  • scripts/CI/linters/pint.yml — source job.
  • CI/linters/pint.yml — assembled output.
  • README.md — new catalog row.

Verification

  • bats tests/linters/pint.bats → 3/3 pass.
  • assemble-ci.sh regenerates cleanly — existing CI/linters/*.yml unchanged; only the new file added.
  • markdownlint README.md → clean.

Closes #37


The task was generated using the MCP server — prog-time/mcp-github-issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[FEATURE] Add Pint linter snippet (Laravel/PHP code style)

1 participant