Do not worry about code style fixes

Earlier this year I installed Fabiens php-cs-fixer on my continuous integration server. So at each build I checked if there were any code style errors, if so I failed the build. Easy as pie and our source code were always nice and clean. But this new feature changed my workflow. My new workflow looks like this:

  • Write code
  • Commit & push code
  • [some time later]
  • Received a build error report
  • I ran php-cs-fixer
  • Commit & Push

I always seams to forget the to run php-cs-fixer before I push my code. The solution is call git hooks. I can tell git that “For this repository, run this script before each commit”. I edit the fileĀ .git/hooks/pre-commit and add the following line:


git diff --name-only --diff-filter=MA HEAD~1 | grep -e "\.php\|\.sh\|\.twig\|\.js\|\.css\|\.md$" | xargs -L1 php-cs-fixer --fixers=-phpdoc_to_comment --level=symfony -q fix

This require you to have php-cs-fixer script in your path. What the script does it it takes all files modified since last commit, filter out php, sh, twig, js, css and md files and gives the rest to php-cs-fixer. I have turned off the ‘phpdoc_to_comment’ fix.

Every time I commit in this repository the php-cs-fixer will make sure I follow the coding standards.

You can do the same globally, but when you fetch a third party repository and do a quick fix you don’t want to change all the coding standards in the files you edit.

Submit a Comment

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>