Jingga/phpOMS
1
0
Fork 0
mirror of https://github.com/Karaka-Management/phpOMS.git synced 2026-01-11 17:58:41 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Fixed line endings

Browse Source
This commit is contained in:
Dennis Eichhorn 2018-06-22 16:31:00 +02:00
parent 3ab5c4ce95
commit 563e6c8631
1 changed files with 26 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

52
CONTRIBUTING.md
View File

@ -1,27 +1,27 @@
# Contributing
## Code Style & Best Practices
For the code style and best practices please have a look at the developer-guide [https://github.com/Orange-Management/Developer-Guide](https://github.com/Orange-Management/Developer-Guide). Especially the `standards` should be followed for a successful pull request.
## How Can I Contribute
### Suggestions
If you have a good idea for improvement feel free to create a new issue with all the relevant information.
### Issues
Feel free to grab any open issue implement it and create a new pull request.
### Code Style
Not always are the defined coding style standards upheld, if you notice that simply create a new pull request with the fix.
### Code Coverage
While code coverage is just a metric it is still appreciated to cover as many files and code paths as possible. Just have a look at the code coverage and implement missing unit tests.
### Freatures
# Contributing
## Code Style & Best Practices
For the code style and best practices please have a look at the developer-guide [https://github.com/Orange-Management/Developer-Guide](https://github.com/Orange-Management/Developer-Guide). Especially the `standards` should be followed for a successful pull request.
## How Can I Contribute
### Suggestions
If you have a good idea for improvement feel free to create a new issue with all the relevant information.
### Issues
Feel free to grab any open issue implement it and create a new pull request.
### Code Style
Not always are the defined coding style standards upheld, if you notice that simply create a new pull request with the fix.
### Code Coverage
While code coverage is just a metric it is still appreciated to cover as many files and code paths as possible. Just have a look at the code coverage and implement missing unit tests.
### Freatures
You have a good idea for a feature and can implement it yourself, go ahead and create a new pull request.