Skip to content

Latest commit

 

History

History
89 lines (56 loc) · 3.55 KB

CONTRIBUTING.md

File metadata and controls

89 lines (56 loc) · 3.55 KB
Raw

Contributing

Contributions are welcome and will be fully credited.

Please read and understand the contribution guide before creating an issue or pull request.

Etiquette

This project is open source, and as such, the maintainers give their free time to build and maintain the source code held within. They make the code freely available in the hope that it will be of use to other developers. It would be extremely unfair for them to suffer abuse or anger for their hard work.

Please be considerate towards maintainers when raising issues or presenting pull requests. Let's show the world that developers are civilized and selfless people.

It's the duty of the maintainer to ensure that all submissions to the project are of sufficient quality to benefit the project. Many developers have different skillsets, strengths, and weaknesses. Respect the maintainer's decision, and do not be upset or abusive if your submission is not used.

Viability

When requesting or submitting new features, first consider whether it might be useful to others. Open source projects are used by many developers, who may have entirely different needs to your own. Think about whether or not your feature is likely to be used by other users of the project.

Procedure

Before filing an issue:

  • Attempt to replicate the problem, to ensure that it wasn't a coincidental incident.
  • Check to make sure your feature suggestion isn't already present within the project.
  • Check the pull requests tab to ensure that the bug doesn't have a fix in progress.
  • Check the pull requests tab to ensure that the feature isn't already in progress.

Before submitting a pull request:

  • Check the codebase to ensure that your feature doesn't already exist.
  • Check the pull requests to ensure that another person hasn't already submitted the feature or fix.

Requirements

If the project maintainer has any additional requirements, you will find them listed here.

  • PSR-4 Coding Standard;

  • Add tests! - Your patch won't be accepted if it doesn't have tests;

  • Document any change in behaviour - Make sure the README.md and any other relevant documentation are kept up-to-date;

  • Consider our release cycle - We try to follow SemVer v2.0.0. Randomly breaking public APIs is not an option;

  • Gitflow Workflow - To be consistent, this project follows the workflow pattern, be sure to use it when sending any pull requests.

  • One pull request per feature - If you want to do more than one thing, send multiple pull requests.

How to?

First, fork this repository. Then, at develop branch, create a new feature branch:

# -> Make sure you are at develop branch
git checkout develop
# <- Pull develop branch before create a new branch
git pull origin develop
# -> Create the new branch where <name> is a name which identifies your branch
git checkout -b feature/<name>

In the feature/<name> branch you can make many commits as you need:

# == To things work great, always do commits, never mind about them, just organize yourself
git add -A
git commit -m "<message>"

After your work is done, push feature/<name> to your origin repo, and make a pull request from it.

Tests

This library uses the PHPUnit. We carry out tests of all the main classes of this application.

vendor/bin/phpunit

You must always run tests with all PHP versions from 7.2 and greater.

php7.2 vendor/bin/phpunit
php7.3 vendor/bin/phpunit
php7.4 vendor/bin/phpunit
php8.0 vendor/bin/phpunit

Happy coding!