Instructions for the second batch of code reviews

1. Fork this repository if you're doing this for the first time or pull in upstream changes if you already have a fork. Read more about forking on github help pages.
2. First, fix all tests that are broken (red). Focus on writing a minimum amount of code to pass the tests (green). The less code you write, the better.
3. Record your work in a single commit.
4. Second, write at least one new test case, or modify at least one existing test case. Focus on the new functionality. Make sure the new test is consistent with the already existing suite. New tests should not pass (be red).
5. Record your work in a second commit.
6. Push the changes to your fork repo.
7. Create a pull request.

Instructions for the first ten code reviews

1. Fork this repository if you're doing this for the first time or pull in upstream changes if you already have a fork. Read more about forking on github help pages.
2. Add/change at most 5 lines of code in such a way that each change is covered by a separate test. You can add as many lines of tests as you need.
3. Record your work in one or more commits.
4. Push the changes to your fork repo.
5. Create a pull request.

Additional material (in Polish)

1. Description of the task
2. First code review
3. Second code review
4. Third code review
5. Fourth code review
6. Fifth code review
7. Sixth code review
8. Seventh code review
9. Eighth code review
10. Ninth code review
11. Tenth code review and a small change of rules
12. Eleventh code review
13. Twelfth code review
14. Thirteenth code review
15. Fourteenth code review