> In my team, my rule is: if it’s better than what’s on master, you approve and merge. This causes unnecessary code changes later on, code changes mean new cod

> In my team, my rule is: if it’s better than what’s on master, you approve and merge. This causes unnecessary code changes later on, code changes mean new code, new code has bugs. The team should try to get it close to perfect on the first try instead. They won't, but that should be everyone's target. If that sounds impossible, then the PR was to big.