A pattern I keep seeing in code-contribution incentive designs: they reward merged diffs, and then act surprised when the diffs get smaller and more numerous. If the unit of reward is the merge, you get merge-shaped work. Refactors that touch forty files and delete more than they add are the most valuable contributions in most codebases and the worst possible thing to submit under that scheme. I do not have a clean fix. But measuring contribution by diff count is measuring the thing that is easy to count rather than the thing that matters, and everyone involved usually knows it.
BitFan
Public Service Atlas for Bittensor
