Skip to content

Latest commit

 

History

History
189 lines (149 loc) · 4.68 KB

CONTRIBUTING.md

File metadata and controls

189 lines (149 loc) · 4.68 KB
Raw

Contributing

When contributing to this repository send a new pull request. If your change is big or complex, or you simply want to suggest an improvement, please discuss the change you wish to make via an issue.

Please note we have a code of conduct. Please follow it in all your interactions with the project.

Pull Request Process

  • Provide good commit messages describing what you've done.
  • Provide tests for any code you write.
  • Make sure all tests are passing.
  • Prefer phive, phar or composer-bin-plugin installation over composer global installations to avoid dependency conflicts.
  • Update the resources/*.json files with any new tools'd like to add.
  • Update README.md with any new tools you added (php bin/devkit.php update:readme).

Adding a new tool

To add support for a new tool, add it to the list in one of the json files in the resources/ folder:

{
  "name": "behat",
  "summary": "Helps to test business expectations",
  "website": "http://behat.org/",
  "command": {
    "composer-bin-plugin": {
      "package": "behat/behat",
      "namespace": "behat"
    }
  },
  "test": "behat --version",
  "tags": ["testing", "test", "bdd"]
}

Each tool should have the following properties specified:

  • name - name of the tool, most of the time the name of executable;
  • summary - shortly stated purpose of the tool;
  • website - link to the tool's website;
  • command - the command to install the tool. See supported commands below;
  • test - the command to verify if the tool is installed. Most of the time it will be the command to show the version or help;

Once you added a new tool to the list, update the list in README.md by running the following command:

php bin/devkit.php update:readme

Commands

There are several supported ways to install tools. All of them are listed below in order of preference.

phive

Downloads a phar for the given alias using phive and puts it into the specified location.

{
  "command": {
    "phive-install": {
      "alias": "dephpend",
      "bin": "%target-dir%/dephpend",
      "sig": "76835C9464877BDD"
    }
  }
}

sig is optional, but it is recommended if the phar is signed.

phar-download

Downloads a phar from the given URL and puts it into the specified location.

{
  "command": {
    "phar-download": {
      "phar": "https://github.com/phpspec/phpspec/releases/download/4.3.0/phpspec.phar",
      "bin": "/usr/local/bin/phpspec"
    }
  }
}

file-download

Downloads a file from the given URL and puts it into the specified location.

{
  "command": {
    "file-download": {
      "url": "https://github.com/vimeo/psalm/releases/download/2.0.0/psalm.phar.asc",
      "file": "/usr/local/bin/psalm.phar.asc"
    }
  }
}

composer-bin-plugin

The composer-bin-plugin method uses the bamarni/composer-bin-plugin to install the package in isolated directory. Thanks to the isolation we're less likely to run into problem with conflicting dependencies between tools.

{
  "command": {
    "composer-bin-plugin": {
      "package": "behat/behat",
      "namespace": "behat",
      "links": {"/tools/behat": "behat"}
    }
  }
}

The links attribute is optional, but it's recommended for packages that provide commands.

box-build

Uses box to build a phar and puts it into the specified location. It will clone the given repository and checkout the latest tag if available.

{
  "command": {
    "box-build": {
      "repository": "https://github.com/behat/behat.git",
      "phar": "behat.phar",
      "bin": "/usr/local/bin/behat"
    }
  }
}

composer-global-install

Uses the composer global require command to install a composer package globally.

{
  "command": {
    "composer-global-install": {
      "package": "bmitch/churn-php"
    }
  }
}

composer-install

Clones the specified repository, checkouts the latest tag (if available), and runs composer install inside. Mostly useful with applications.

{
  "command": {
    "composer-install": {
      "repository": "https://github.com/Qafoo/QualityAnalyzer.git"
    }
  }
}

Executing multiple commands

It's sometimes useful to run multiple installation commands i.e. when downloading a phar and its signature.

{
  "command": {
    "file-download": {
      "url": "https://github.com/vimeo/psalm/releases/download/2.0.0/psalm.phar.asc",
      "file": "/usr/local/bin/psalm.phar.asc"
    },
    "phar-download": {
      "phar": "https://github.com/vimeo/psalm/releases/download/2.0.0/psalm.phar",
      "bin": "/usr/local/bin/psalm"
    }
  }
}