Created separate code of conduct document and renamed files back to capital, so that they are easier to find.

This commit is contained in:
alext 2018-11-03 17:24:51 +01:00
parent 650fe4e36f
commit 1178e9e58a
5 changed files with 18 additions and 18 deletions

View file

@ -1,21 +1,4 @@
# Contributing # Code of Conduct
When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other
method with the owner of this repository before making a change.
Please note we have a code of conduct, please follow it in all your interactions with the project.
## Pull Request Process
1. Ensure any install or build dependencies are removed before the end of the layer when doing a build.
2. Ensure that your changes comply with the project's coding guidelines and that it's sufficiently documented.
3. Update the README.md with details of changes to the interface, this includes new environment variables, exposed
ports, useful file locations and container parameters.
4. Target the develop branch for your Pull Requests as this is were new changes are introduced.
4. After being successfully reviewed pull requests will be merged to develop branch and will finally be included in an
upcoming release.
## Code of Conduct
### Our Pledge ### Our Pledge

17
CONTRIBUTING.md Normal file
View file

@ -0,0 +1,17 @@
# Contributing
When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other
method with the owner of this repository before making a change.
Please note we have a code of conduct, please follow it in all your interactions with the project.
## Pull Request Process
1. Ensure any install or build dependencies are removed before the end of the layer when doing a build.
2. Ensure that your changes comply with the project's coding guidelines and that it's sufficiently documented.
3. Update the README.md with details of changes to the interface, this includes new environment variables, exposed
ports, useful file locations and container parameters.
4. Target the develop branch for your Pull Requests as this is were new changes are introduced.
4. After being successfully reviewed pull requests will be merged to develop branch and will finally be included in an
upcoming release.

View file