First off, thank you for considering contributing to OTE v2. It's people like you that make open source such a great community.
If you find a bug, please open an issue on our GitHub Issues page. Please include as much detail as possible, including:
- A clear and descriptive title.
- A description of the problem.
- Steps to reproduce the bug.
- Any relevant screenshots or error messages.
If you have an idea for a new feature or an enhancement to an existing one, please open an issue on our GitHub Issues page. Please provide a clear and detailed explanation of the feature you're suggesting and why it would be valuable.
Unsure where to begin contributing to OTE v2? You can start by looking through the good-first-issue and help-wanted issues.
- Fork the repository on GitHub.
- Clone your fork to your local machine.
- Create a new branch for your changes:
git checkout -b your-branch-name. - Make your changes.
- Run the tests to make sure everything is still working:
composer test. - Run the code formatter to ensure your code follows our style guide:
composer format. - Run the static analyzer to check for potential bugs:
composer analyse. - Commit your changes with a clear and descriptive commit message.
- Push your changes to your fork:
git push origin your-branch-name. - Open a pull request to the
masterbranch of the main repository.
This project uses Laravel Pint to enforce a consistent coding style. Before you commit your changes, please run the code formatter:
composer formatThis project uses Pest for testing. To run the test suite, use the following command:
composer testThis project uses PHPStan with the Larastan extension for static analysis. To run the static analyzer, use the following command:
composer analyseThank you for your contribution!