

It obviously depends on your exact git workflow, but my last team had things setup so that the code content of a MR was automatically squashed on merge, and the text if the MR itself was automatically set as the content of the new singular git commit.
This was largely the best of both worlds because your commits could have almost any text, and the description of what changed could be updated as needed when making the MR. But it ultimately ended up in the git history where it belonged.
Of course, I still had some trouble trying to get the team to describe their changes well in the MR at times - but that’s a different problem entirely.
Yeah, every time there is a post on the topic, moderators say that the tools they have are insufficient.
It’d be great to have some community focus on that going forward, whether through direct Lemmy changes or creating better bot mod tools. I’m not in a position to contribute right now but maybe in a few months.
There is a subset of Lemmy that absolutely hates any idea of automod tools because it reminds them too much of issues they had with Reddit. But as Lemmy grows (and given it’s volunteer nature) it feels inescapable at some point.