At Kraken Tech we use GitHub pull requests for our reviews. Over the years we’ve adopted a set of conventions to make sure we get the most out of the reviewing process.
We’ve recently revamped them and published them on our public conventions. Take a look, and feel free to use / fork for your own team.
Here are three of my favourites:
- Sharing Power Updates using Amazon EventBridge Pipes
- Using formatters and linters to manage a large codebase
- Patterns of flakey Python tests
- Integrating Asana and GitHub
- Durable database transactions in Django
- Python interfaces a la Golang
- Beware changing the "related name" of a Django model field
- Our in-house coding conventions
- Recommended Django project structure
- Using a custom Sentry client
- Improving accessibility at Octopus Energy
- Django, ELB health checks and continuous delivery
- Organising styles for a React/Django hybrid
- Testing for missing migrations in Django
- Hello world, would you like to join us?