frappe_docker/CONTRIBUTING.md

# Contribution Guidelines

## Branches

* *master*:  images on the master branch are built monthly and with github action triggered by ERPNext release.
* *develop*: images on this branch are built daily and when PR is merged into develop.

# Pull Requests

Please **send all pull request exclusively to the *develop*** branch.
When the PR are merged, the merge will trigger the image build automatically.

Please test all PR as extensively as you can, considering that the software can be run in different modes:

* with docker-compose for production
* with or without Nginx proxy
* with VScode for testing environments

Every once in a while (or with monthly release) develop will be merged into master.

There is Github Action is configured on ERPNext repository. Whenever there is a ERPNext release it will trigger a build on master branch of frappe_docker repo to generate images for released version.

When a PR is sent, the images are built and all commands are tested.

If update or fixes to documentation are pushed use `[skip travis]` anywhere in commit message to skip travis.

## Reducing the number of branching and builds :evergreen_tree: :evergreen_tree: :evergreen_tree:

Please be considerate when pushing commits and opening PR for multiple branches, as the process of building images (triggered on push and PR branch push) uses energy and contributes to global warming.


# Documentation

Place relevant markdown file(s) in the `docs` directory and index them in README.md located at the root of repo.
Add contributing.md by github standards 2020-03-24 15:00:46 +00:00			`# Contribution Guidelines`
docs: organize docs break down readme into multiple files organize in docs directory [skip travis] 2020-06-13 10:03:06 +00:00
Add contributing.md by github standards 2020-03-24 15:00:46 +00:00			`## Branches`

docs: organize docs break down readme into multiple files organize in docs directory [skip travis] 2020-06-13 10:03:06 +00:00			`* master: images on the master branch are built monthly and with github action triggered by ERPNext release.`
			`* develop: images on this branch are built daily and when PR is merged into develop.`
Add contributing.md by github standards 2020-03-24 15:00:46 +00:00
			`# Pull Requests`

docs: organize docs break down readme into multiple files organize in docs directory [skip travis] 2020-06-13 10:03:06 +00:00			`Please *send all pull request exclusively to the develop*** branch.`
Add contributing.md by github standards 2020-03-24 15:00:46 +00:00			`When the PR are merged, the merge will trigger the image build automatically.`

			`Please test all PR as extensively as you can, considering that the software can be run in different modes:`
docs: organize docs break down readme into multiple files organize in docs directory [skip travis] 2020-06-13 10:03:06 +00:00
Add contributing.md by github standards 2020-03-24 15:00:46 +00:00			`* with docker-compose for production`
			`* with or without Nginx proxy`
			`* with VScode for testing environments`

docs: organize docs break down readme into multiple files organize in docs directory [skip travis] 2020-06-13 10:03:06 +00:00			`Every once in a while (or with monthly release) develop will be merged into master.`

			`There is Github Action is configured on ERPNext repository. Whenever there is a ERPNext release it will trigger a build on master branch of frappe_docker repo to generate images for released version.`

			`When a PR is sent, the images are built and all commands are tested.`

			If update or fixes to documentation are pushed use `[skip travis]` anywhere in commit message to skip travis.

			`## Reducing the number of branching and builds :evergreen_tree: :evergreen_tree: :evergreen_tree:`
Add contributing.md by github standards 2020-03-24 15:00:46 +00:00
			`Please be considerate when pushing commits and opening PR for multiple branches, as the process of building images (triggered on push and PR branch push) uses energy and contributes to global warming.`


docs: organize docs break down readme into multiple files organize in docs directory [skip travis] 2020-06-13 10:03:06 +00:00			`# Documentation`
Add contributing.md by github standards 2020-03-24 15:00:46 +00:00
docs: organize docs break down readme into multiple files organize in docs directory [skip travis] 2020-06-13 10:03:06 +00:00			Place relevant markdown file(s) in the `docs` directory and index them in README.md located at the root of repo.