CONTRIBUTING.md

Contributing Guidelines

First off, thanks for taking the time to contribute!

Getting Started

When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the core team before making a change.

• Make sure you have a GitHub account.
• Submit a GitHub issue for your issue if one does not already exist.
  • A issue is not necessary for trivial changes.
• Fork the repository on GitHub.
  • Configuring a remote for a fork
  • Syncing a fork
    • git fetch upstream
    • git checkout master
    • git merge upstream/master
  • Merging an upstream repository into your fork
    • git checkout master
    • git pull upstream master
    • Commit the merge
    • git push origin master
• When working on an issue, create a new branch from master named for issue number or custom name. Name the branch issue/<issue-number> or issue/<custom-name>. For example issue/22 for fixing issue #22.
• Make your changes.
  • Follow the Style Guides.
  • Avoid platform-dependent code.
  • Add tests if your changes contains new, testable behavior.
  • Make the tests pass.
• Create a pull request to the repository.

Tips and tricks for using the Git

• GitHub Cheat Sheet
• git-tips

Key branches

• master is the latest, deployed version

Composer

https://getcomposer.org/doc/04-schema.md

In all cases when composer.json file is updated, add composer.json and composer.lock files to the same commit.

Each package must contain specific version. Don't use * and @dev versions.