> I also see more and more pull request summaries clearly written by machines for machines. They are rich in detail: this was changed to that, these things were split, those things were merged, this was left untouched, tests were added for this, and so on. But I’m left asking: Why are we doing this? What is the value? How risky or urgent is this work? Where do you want my input? What should I pay attention to?
My own solution for this (for now at least) is to add a preamble section “AI;DR” to PR descriptions, filling what a TL;DR section would have done in the past. I’ve socialized to my peers that no part of such a section will be written by AI, and it should contain exactly this missing high-level content described by the author.
My own solution for this (for now at least) is to add a preamble section “AI;DR” to PR descriptions, filling what a TL;DR section would have done in the past. I’ve socialized to my peers that no part of such a section will be written by AI, and it should contain exactly this missing high-level content described by the author.