From b2ab08b1b5666ea6a10b5a9c1390b289b15005fc Mon Sep 17 00:00:00 2001 From: Adrien Crivelli Date: Thu, 2 Nov 2017 15:50:01 +0900 Subject: [PATCH] Mention `composer fix` in contributing guide --- CONTRIBUTING.md | 1 + 1 file changed, 1 insertion(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 56b71ee1..62f07721 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -5,6 +5,7 @@ If you would like to contribute, here are some notes and guidelines: - All new development happens on feature/fix branches referenced with the GitHub issue number, and are then merged to the develop branch; so the develop branch is always the most up-to-date, working code - The master branch only contains tagged releases - If you are going to be submitting a pull request, please fork from develop, and submit your pull request back as a fix/feature branch referencing the GitHub issue number + - Code style might be automatically fixed by `composer fix` - All code changes must be validated by `composer check` - [Helpful article about forking](https://help.github.com/articles/fork-a-repo/ "Forking a GitHub repository") - [Helpful article about pull requests](https://help.github.com/articles/using-pull-requests/ "Pull Requests")