Rebase, history and reviews
Comes up in: Hiring manager, Behavioural, Code review
This concept is being written. It gets the full five steps — explanation, predict, interview angle, practice with tests, and review cards. Here is exactly what it will cover, so you can study it elsewhere in the meantime.
What it covers
- rebase vs merge vs squash
- interactive rebase
- conventional commits
git bisect- good PR size and descriptions
- code review culture and giving feedback
Words you will know
What you will practise
- bisect a regression
- clean up a branch history
Interview questions this answers
- Merge vs rebase vs squash: when do you use each?
- How do you use
git bisect? - What makes a good code review?