so I guess the way to game this is to figure out what the changes need to be, maybe have two versions of the repo make changes in version one determine is good, take out branch, copy paste and then you have short time to diff. Of course you still have to argue why you had so few tickets taken, but that could be due to meeting time.
just going off the idea that any new metric instead becomes the target, and not actually the improvement the metric is supposed to measure.
so I guess the way to game this is to figure out what the changes need to be, maybe have two versions of the repo make changes in version one determine is good, take out branch, copy paste and then you have short time to diff. Of course you still have to argue why you had so few tickets taken, but that could be due to meeting time.
just going off the idea that any new metric instead becomes the target, and not actually the improvement the metric is supposed to measure.