Update 'CONTRIBUTING.md'
This commit is contained in:
parent
1cf0a9d8db
commit
f94d92e39e
@ -36,11 +36,12 @@ Before sending your pull request for review, make sure your changes are consiste
|
|||||||
* Include unit tests when you contribute new features, as they help to:
|
* Include unit tests when you contribute new features, as they help to:
|
||||||
* Prove that your code works correctly.
|
* Prove that your code works correctly.
|
||||||
* Guard against future breaking changes to lower the maintenance cost.
|
* Guard against future breaking changes to lower the maintenance cost.
|
||||||
|
|
||||||
* Bug fixes also generally require unit tests, because the presence of bugs usually indicates insufficient test coverage.
|
* Bug fixes also generally require unit tests, because the presence of bugs usually indicates insufficient test coverage.
|
||||||
* Keep backward compatibility in mind when you change code in CERC Libs, and if you need to broke the backward compatibility, please ensure that you:
|
* Keep backward compatibility in mind when you change code in CERC Libs, and if you need to broke the backward compatibility, please ensure that you:
|
||||||
|
* Clearly indicate which features are affected by your changes.
|
||||||
1. Clearly indicate which features are affected by your changes.
|
* Technical reasons for the changes.
|
||||||
2. Technical reasons for the changes.
|
|
||||||
* Tests should follow the
|
* Tests should follow the
|
||||||
[testing best practices](CONTRIBUTING.md#user-content-testing-best-practices)
|
[testing best practices](CONTRIBUTING.md#user-content-testing-best-practices)
|
||||||
guide.
|
guide.
|
||||||
|
Loading…
Reference in New Issue
Block a user