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.

Super cool project. FYI it does require converting your ebooks to a special format.

I suspected as much since it’s using an Arduino Mega - very battery efficient I’m sure, but very underpowered.