Closed jrfnl closed 4 years ago
@jmarcil I've reverted the example commands for now as discussed above
This includes reverting (updating) the example output to be in line with the actual command in the readme.
The other changes related to the rulesets discussed above will/should be addressed in separate PRs.
P.S.: I rebased the PR to see the Travis build being triggered, but it appears to not be turned on correctly yet. Let me know if you need help getting it working.
Thanks!
I actually never activated it on Travis-CI.. working on it right now.
@jmarcil Should be a case of just toggling the switch for the repo. Let me know if you need help/screencast on how to do it.
Should be 😄
I don't know why, but I couldn't see FloeDesignTechnologies in my organizations (yet I can see another one), but I could still browse https://travis-ci.org/github/FloeDesignTechnologies and activate the repo from there.
Build is working as far as I can tell: https://travis-ci.org/github/FloeDesignTechnologies/phpcs-security-audit
@jmarcil Excellent! Glad you got it working. Will be helpful for adding the rest of the checks proposed in #56 and making sure the automated tests are all running & passing.
--standard=Security
instead of pointing to a specific example ruleset.