# Contribution guide I’m really excited that you are interested in contributing to Ignico. Before submitting your contribution though, please make sure to take a moment and read through the following guidelines. ## Development setup ### Clone project ``` git clone git@github.com:ignicoapp/ignico-wordpress.git cd ignico-wordpress ``` ### Copy dotenv and fill with your properties ``` cp .env.example .env ``` ### Install dependencies ``` composer install ``` During installation WordPress is downloaded to wordpress directory and current directory is self symlinked to wordpress/wp-content/plugins. Pointing your webserver vhost to wordpress directory give you fully working WordPress instance with Ignico WordPress plugin installed. ### Setup WordPress ``` ./vendor/bin/phing wp:init ``` This command will install WordPress with configuration from .env file. After installation you should have fully working WordPress instance with Ignico WordPress plugin activated. ### Code inspection and tests Be sure to execute code inspection and test before before making a pull request. ``` ./vendor/bin/phing inspect tests ``` ## Commit message guidelines A well-structured and described commit message helps better maintain open source project. * current developers and users can quickly understand what new changes are about * future developers have a clear history of changes in the code * changelog is automatically generated from commit messages Commit message is divided into sections **type**, **scope**, **subject**, **body**, **footer**. Only **type** and **subject** are required. ``` ():