diff options
| author | kwgchi <eiichi.kendoruki@gmail.com> | 2020-07-10 23:45:26 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-07-10 16:45:26 +0200 |
| commit | 229a623849da617abd9afc3f30ba6c612b4c04c2 (patch) | |
| tree | c6474f9a95aa5209173b35c67dcd76b0b9747af5 | |
| parent | 371b416ac818412909243d10a66c20db3eaa23f3 (diff) | |
| download | Nim-229a623849da617abd9afc3f30ba6c612b4c04c2.tar.gz | |
Update readme.md (#14953)
| -rw-r--r-- | readme.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/readme.md b/readme.md index f529c0df0..94241822f 100644 --- a/readme.md +++ b/readme.md @@ -138,7 +138,7 @@ you should familiarize yourself with the following repository structure: If you are not familiar with making a pull request using GitHub and/or git, please read [this guide][pull-request-instructions]. -Ideally you should make sure that all tests pass before submitting a pull request. +Ideally, you should make sure that all tests pass before submitting a pull request. However, if you are short on time, you can just run the tests specific to your changes by only running the corresponding categories of tests. Travis CI verifies that all tests pass before allowing the pull request to be accepted, so only @@ -146,7 +146,7 @@ running specific tests should be harmless. Integration tests should go in ``tests/untestable``. If you're looking for ways to contribute, please look at our [issue tracker][nim-issues]. -There are always plenty of issues labelled [``Easy``][nim-issues-easy]; these should +There are always plenty of issues labeled [``Easy``][nim-issues-easy]; these should be a good starting point for an initial contribution to Nim. You can also help with the development of Nim by making donations. Donations can be |