jenkins/sap-jenkins-library
1
0
Fork 0
mirror of https://github.com/SAP/jenkins-library.git synced 2024-12-12 10:55:20 +02:00
Code Issues Releases Activity

Fix CONTRIBUTING.md

Browse Source 
Fix some spelling errors.
This commit is contained in:
Oliver Feldmann 2017-11-27 13:09:29 +01:00
parent 98a08968af
commit 772fc50b50
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
CONTRIBUTING.md
View File

@ -8,14 +8,14 @@ There are two primary ways to help:
Use the issue tracker to suggest feature requests, report bugs, and ask questions. This is also a great way to connect with the developers of the project as well as others who are interested in this solution.
Use the issue tracker to find ways to contribute. Find a bug or a feature, mention in the issue that you will take on that effort, then follow the Changing the code-base guidance below.
Use the issue tracker to find ways to contribute. Find a bug or a feature, mention in the issue that you will take on that effort, then follow the "Changing the code-base" guidance below.
## Changing the code-base
Generally speaking, you should fork this repository, make changes in your own fork, and then submit a pull-request. All new code should have thoroughly tested to validate implemented features and the presence or lack of defects and it should come with an adequate documentation.
Generally speaking, you should fork this repository, make changes in your own fork, and then submit a pull-request. All new code should have been thoroughly tested end-to-end in order to validate implemented features and the presence or lack of defects.
### Tests
All pipeline library coding MUST come with an automated test. as well as adequate documentation.
All pipeline library coding _must_ come with automated unit tests.
### Documentation
The contract of functionality exposed by a library functionality needs to be documented, so it can be properly used.