I’ve been using copilot and find it’s suggestions are perfectly cromulent.

Grey beards merge and increment (ie: senior devs unite and rise up)

This is the reason for me. Sometimes I don’t want to step through the code and just want to scan through a giant list of output.

Hollywood hacking or updating packages?

We squash when merging. Final git history is super clean and linear.

Rebase all of your work branches onto HEAD so that conflicts require refactoring the first commit where things don’t match up. This can make conflicts easier to deal with (in my humble opinion) since you deal with conflicts earlier in your commit history as opposed to at the end after ALL of your changes are made.

Plus a linear history is super nice to work with later on.