What You’ll Learn
The two-pipeline structure: ci.yml and quality.yml
Why separating fast feedback from deep analysis matters
The optimized ci.yml – tests + style, under 3 minutes
The optimized quality.yml – Larastan + security audit
Composer and PHP caching strategies
Common mistakes in Laravel CI setups
Two Pipelines, Two Purposes
Most teams start with one CI file that does everything: lint, test, static analysis, security audit. The problem: when tests fail, you wait 4 minutes before seeing a failure that a 10-second linter run would have caught first. When Larastan fails on a trivial type error, the same failure blocks the PR whether it’s a typo or a logic flaw.
Two pipelines solve this:
ci.yml – Fast feedback (< 3 minutes). Runs on every push to every branch. Tests + code style. If this fails, you don’t merge.
quality.yml – Deep analysis (< 5 minutes). Runs on push to main and on PRs. Larastan + security audit.…