But I'll tell you what does happen from merging other's changes into my local more often than my peers:
I'm usually the first to be "hit" by bad code changes merged by my peers -- which they've often done without even compiling or running their changes.
But actually, I'm OK with that.
(The bosses aren't. But what do they know?)
I'm a senior person. So I go over and have a private conversation with the coder who did that. And I help them fix it before it hits others.
@JeffGrigg - you're one of the good ones, Jeff 🏆
Sounds like it would be good to automate those checks so developers get their feedback quickly, with a little note attached that says: "If you need help, go ask Jeff."
Yea; we automate those things.
Now, with BitBucket, it physically prevents you from merging until it compiles and all the tests pass.
But *Just Last Week* some changes got through that, and knocked me and some other team members out of commission for one to three days. (It somehow corrupted our branches and development environments too. Crazy, but true!)
And the tools can't solve all the problems: We need to WRITE the tests, too!