# Improving Code Reviews


## What We're Missing - [ ] Standard branch names - [ ] Descriptive PR names - [ ] Helpful PR descriptions - [ ] Fast turn arounds on CRs - [ ] Clear overview on PR status

## Why Bother? - Makes on-boarding easier. - Aligns our standards and way of working. - Avoid a single point of failure on a project for a developer.

## The Process 1 - Commit your changes on a branch. `feature/{ticket number}-{ticket name}`

### The Process 2: ## Starting a PR - Push and start a Pull Request to `develop`. - Name your PR: `{ticket number}: {ticket name}`

### The Process 3: ## Writing a description - An overview of why the change is necessary. - The scope of the change. - Where special attention is required. - Changes that need clarification. - Details that may help reviewers. Read this: [How to Conduct Effective Code Reviews](https://blog.digitalocean.com/how-to-conduct-effective-code-reviews/)