mirror of
https://github.com/Karaka-Management/jsOMS.git
synced 2026-01-24 15:38:41 +00:00
Improve coc and contribution guide
This commit is contained in:
parent
e92928aaad
commit
ea94fafcdd
1
.github/contributing.md
vendored
1
.github/contributing.md
vendored
|
|
@ -1 +0,0 @@
|
|||
A developer and contribution documentation can be found at https://orange-management.gitbooks.io/developer-guide/content/index.html.
|
||||
27
CONTRIBUTING.md
Normal file
27
CONTRIBUTING.md
Normal file
|
|
@ -0,0 +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
|
||||
|
||||
You have a good idea for a feature and can implement it yourself, go ahead and create a new pull request.
|
||||
Loading…
Reference in New Issue
Block a user