You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -104,7 +104,7 @@ Please try to keep your individual changes as minimal and focussed on the issue
104
104
If you discover that the scope of your contribution is growing larger than expected you might want to split the changes into multiple separate contributions to allow a more focussed discussion and review.
105
105
106
106
It is usually a great idea and often required to add tests for your changes.
107
-
This allows us to quickly validate that the changes are working as intended and also guarantees that they wont be broken by other future updates.
107
+
This allows us to quickly validate that the changes are working as intended and also guarantees that they won't be broken by other future updates.
108
108
For small and targeted functional changes, e.g. supporting a new URL schema, a [unit test](#unit-tests) may be enough.
109
109
For contributions that change large-scale behaviour, such as dependency caching features, an [integration test](#integration-tests) is more suited.
110
110
Depending on the changes, a combination of both test types may also be appropriate.
0 commit comments