Skip to content

Latest commit

 

History

History
60 lines (38 loc) · 2.35 KB

CONTRIBUTING.md

File metadata and controls

60 lines (38 loc) · 2.35 KB
Raw

Contributing to the Exakat Engine

Workflow

  • Fork the project.
  • Make your bug fix or feature addition.
  • Send a pull request.

Please make sure that you have set up your user name and email address for use with Git. Strings such as silly nick name <root@localhost> look really stupid in the commit history of a project.

Pull requests for bug fixes must be based on the current stable branch whereas pull requests for new features must be based on the current alpha branch (when 5.0 is the current stable branch, then 5.1 is the current beta branch and 5.2 is the current alpha branch).

We are trying to keep backwards compatibility breaks in PHPUnit to an absolute minimum. Please take this into account when proposing changes.

Due to time constraints, we are not always able to respond as quickly as we would like. Please do not take delays personal and feel free to remind us if you feel that we forgot to respond.

Coding Guidelines

This project comes with a configuration file for php-cs-fixer (.php_cs) that you can use to (re)format your sourcecode for compliance with this project's coding guidelines:

$ wget http://get.sensiolabs.org/php-cs-fixer.phar

$ php php-cs-fixer.phar fix

Using PHPUnit from a Git checkout

The following commands can be used to perform the initial checkout of PHPUnit:

$ git clone git://github.com/sebastianbergmann/phpunit.git

$ cd phpunit

Retrieve PHPUnit's dependencies using Composer:

$ wget http://getcomposer.org/composer.phar

$ php composer.phar install

The phpunit script can be used to invoke the PHPUnit test runner:

$ ./phpunit --version

Reporting issues

Please use the most specific issue tracker to search for existing tickets and to open new tickets: