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, and are then merged to the `master` branch once stable; so the `master` branch is always the most up-to-date, working code
 - Tagged releases are made from the `master` branch
 - If you are going to be submitting a pull request, please fork from `master`, 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")
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:`

`master` is the new default branch `master` is now the only permanent branch. Features and fixes should be merged into `master` when stable. Pull requests should be forked from `master`. `develop` branch disappear entirely in favor of temporary features/fixes branches. 2019-01-02 04:23:59 +00:00			- All new development happens on feature/fix branches, and are then merged to the `master` branch once stable; so the `master` branch is always the most up-to-date, working code
			- Tagged releases are made from the `master` branch
			- If you are going to be submitting a pull request, please fork from `master`, and submit your pull request back as a fix/feature branch referencing the GitHub issue number
Mention `composer fix` in contributing guide 2017-11-02 06:50:01 +00:00			- Code style might be automatically fixed by `composer fix`
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")`