2017 © Pedro Peláez
 

library code-sniffer

The coding standards set by the company

image

gatenbysanderson/code-sniffer

The coding standards set by the company

  • Wednesday, February 7, 2018
  • by gatenbysanderson
  • Repository
  • 1 Watchers
  • 0 Stars
  • 10 Installations
  • 0 Dependents
  • 0 Suggesters
  • 0 Forks
  • 0 Open issues
  • 6 Versions
  • 0 % Grown

The README.md

Code Sniffer

The coding standards that have been set and agreed by the development team., (*1)

Licence

Copyright © 2018 GatenbySanderson Ltd., (*2)

This project is open source software released under the terms of the MIT licence: see LICENCE.md., (*3)

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes., (*4)

Prerequisites

  • PHP >=5.6

As this is a private repo, when using composer to require this package - it is assumed your SSH key has already been added to GitHub to authenticate., (*5)

Installing

Start by adding this repo to your projects composer.json file:, (*6)

{
  "repositories": [
    {
        "type": "vcs",
        "url":  "git@github.com:gatenbysanderson/code-sniffer.git",
        "no-api": true
    }
  ]
}

You can then simply require the package as with any other:, (*7)

$ composer require --dev gatenbysanderson/code-sniffer

Running the Sniffer

To run the sniffer, you can either call the command in full:, (*8)

$ vendor/bin/phpcs --standard=vendor/gatenbysanderson/code-sniffer/src/phpcs.xml directory1 [directory2 ...]

Or create a composer script to make life easier:, (*9)

{
  "scripts": {
    "gscs": "phpcs --standard=vendor/gatenbysanderson/code-sniffer/src/phpcs.xml directory1 [directory2 ...]"
  }
}

This allows you to then run:, (*10)

$ composer gscs

Built With

Contributing

All changes must be made through the medium of a pull request., (*11)

  1. Create a feature branch off of the develop branch: feature/my-awesome-feature
  2. Push your commits to the feature branch
  3. Submit a pull request to merge the feature into develop
  4. Once accepted, develop should then be merged into master
  5. master should then be tagged with a new release

Versioning

We use SemVer for versioning. For the versions available, see the tags on this repository., (*12)

The Versions

07/02 2018

dev-master

9999999-dev

The coding standards set by the company

  Sources   Download

proprietary

The Requires

 

by Mubeen Inamdar

07/02 2018

v1.2.0

1.2.0.0

The coding standards set by the company

  Sources   Download

proprietary

The Requires

 

by Mubeen Inamdar

07/02 2018

dev-develop

dev-develop

The coding standards set by the company

  Sources   Download

proprietary

The Requires

 

by Mubeen Inamdar

22/01 2018

v1.1.1

1.1.1.0

The coding standards set by the company

  Sources   Download

proprietary

The Requires

 

by Mubeen Inamdar

18/01 2018

v1.1.0

1.1.0.0

The coding standards set by the company

  Sources   Download

proprietary

The Requires

 

by Mubeen Inamdar

17/01 2018

v1.0.0

1.0.0.0

The coding standards set by the company

  Sources   Download

proprietary

The Requires

 

by Mubeen Inamdar