From a33aa6ab4bb43bbc4725707f859ef7ecfaee23a0 Mon Sep 17 00:00:00 2001 From: Ben Sherred Date: Sat, 25 Nov 2023 18:24:32 +0000 Subject: [PATCH] chore: update CONTRIBUTING formatting --- CONTRIBUTING.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 1825d9a..6f1fa0a 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -41,22 +41,20 @@ Before submitting a pull request: If the project maintainer has any additional requirements, you will find them listed here. -- **[PER Coding Standard](https://github.com/php-fig/per-coding-style/blob/2.0.0/spec.md)** - The easiest way to apply - these conventions is to use the `composer lint` command. +- **[PER Coding Standard](https://github.com/php-fig/per-coding-style/blob/2.0.0/spec.md)** - The easiest way to apply these conventions is to use the `composer lint` command. - **Add tests!** - This helps to ensure the codebase is easily maintable. - **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](https://semver.org/). Randomly breaking public APIs - is not an option. +- **Consider our release cycle** - We try to follow [SemVer v2.0.0](https://semver.org/). Randomly breaking public APIs is not an + option. - **One pull request per feature** - If you want to do more than one thing, send multiple pull requests. - **Send coherent history** - Make sure each individual commit in your pull request is meaningful. If you had to make - multiple intermediate commits while developing, please - [squash them](https://www.git-scm.com/book/en/v2/Git-Tools-Rewriting-History#Changing-Multiple-Commit-Messages) + multiple intermediate commits while developing, please [squash them](https://www.git-scm.com/book/en/v2/Git-Tools-Rewriting-History#Changing-Multiple-Commit-Messages) before submitting. **Happy coding**!