Nothing slows down a project—or a contribution—like pushing your code only to have GitLabCI reject it. Missed coding standards, preventable errors, and style issues waste review cycles and delay releases. Not anymore.
You’ll learn how to bring those same checks into your local environment so you can catch problems before they hit Drupal.org’s pipelines. By running the exact tools GitLabCI uses—ESLint, Stylelint, PHPCS, and PHPStan—you’ll cut down on frustrating back-and-forth, write more consistent code, and keep your contributions moving smoothly.
You don’t need deep expertise: I’ll provide ready-to-use configuration so you can get started right away.
I’ll cover:
- Installing and configuring each linter for Drupal
- Matching GitLabCI behavior locally
- Automating checks for faster feedback
- Catching issues early to speed up reviews and QA
- Extending checks beyond what GitLabCI enforces
Whether you’re submitting your first merge request or keeping client projects clean, these practices will improve your workflow, reduce wasted time, and help the whole Drupal ecosystem move faster.
At the end of this session, attendees will be able to:
- Set up local code-quality tools (ESLint, Stylelint, PHPCS, PHPStan) in a Drupal project with provided configuration.
- Run and automate the same checks used on Drupal.org’s GitLabCI to catch errors early and reduce failed builds.
- Extend these checks to raise internal quality standards and deliver more consistent, maintainable Drupal code.
