6. When should we respond to comments from collaborators and reviewers?
- When their comments address software-breaking bugs
- No need, just resolve the concerns and be done with it
- Always
- Only when a code correction is necessary
7. What is a nit?
- A trivial comment or suggestion
- A couple lines of code
- A repository that is no longer maintained
- An orphaned branch
8. Select common code issues that might be addressed in a code review. (Check all that apply)
- Using unclear names
- Following PEP8 guidelines
- Forgetting to handle a specific condition
- Forgetting to add tests
9. If we've pushed a new version since we've made a recent change, what might our comment be flagged as?
- Accepted
- Resolved
- Outdated
- Merged
10. What are the goals of code review? (Check all that apply)
- Make sure that the contents are easy to understand
- Ensure consistent style
- Build perfect code
- Ensure we don’t forget any important cases
