PHP_CodeSniffer: Travis won't work with custom PHP Standard

I’m new at this, but I tried to add phpcs with Travis and it won’t work. It seems that it’s because i made my own PHP Standard from the code of the PEAR Standard. Is there maybe a way to tell Travis to look into the src/Standard folder in order to see mine

.travis.yml:
script:
  - ./vendor/bin/phpcs ./
Travis build:
$ ./vendor/bin/phpcs ./
ERROR: Referenced sniff "Gampear.Commenting.ClassComment" does not exist

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 18 (8 by maintainers)

Most upvoted comments

It works !! i’m so embarrassed for the typo. Thank you all !!

@gamcoh I’ve had a quick look. You seem to try to register the PHPCS native standards as well. You don’t need to do that. There is also a typo in that line - installed_path vs installed_paths (note the s at the end).

Try changing line 10 to: - ./vendor/bin/phpcs --config-set installed_paths /tmp/Gamzer-PHP-Standard/

Juliette made awesome examples that you can check here: https://github.com/jrfnl/make-phpcs-work-for-you 😃

Ok, I’m writing a PR 😂 Thanks for the tip, have I told you how awesome you are? 😄