Across
- 2. what a primary reviewer should be with the area of code
- 4. no more than needed
- 9. great engineers listen to them
- 10. the desired size of a PR
- 11. needed on every PR
- 12. must be considered and tested
- 13. opportunity for standardization or reuse
- 15. improves quality and facilitates learning
- 18. should be descriptive
- 19. check IntelliJ and eliminate them
- 20. is it a good one?
- 25. should have CRAB and summary
- 26. should summarize the change
- 27. keeps focus off the trivial
Down
- 1. review before adding reviewers
- 3. needed for backports
- 4. explain why not what
- 5. these should be removed
- 6. working together to improve code quality
- 7. considered to get from here to there
- 8. no longer needed
- 14. needed on every pull request
- 16. the PR relation to the whole system
- 17. codifies best practices
- 21. unscripted testing
- 22. a minor comment for education or polish
- 23. enshure it's correct
- 24. should sufficiently cover
- 28. consider customers when user facing