PhpSpreadsheet/CONTRIBUTING.md

# Want to contribute?

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
 - 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")
Keep documentation in a single place and link to it Fixes #191 Closes #192 2017-07-30 14:22:28 +00:00			`# Want to contribute?`

			`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`
Document the prerequisite of `composer check` for contributions 2017-09-11 05:57:12 +00:00			- All code changes must be validated by `composer check`
Keep documentation in a single place and link to it Fixes #191 Closes #192 2017-07-30 14:22:28 +00:00			`- [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")`