If your code gives attack surface by information about what went wrong maybe you should not even deploy anything. If your code needs to be secret to be secure your code is anything but secure.
I hate this attitude. Yeah don't give the user stacktraces on error but if you give it a meaningful headline and go in detail, experienced users will be able to deal with the problem if possible. If you go Microsoft-error of mystic ways you will have people Google "unexpected error e34566xce" and they will see that it has 10 possible reasons so you don't know what even went wrong.
I recently tried to compile an Raspberry pi image. I have no idea what to do when an error occurs. And I am a software developer who should at least have an idea. However goggle helps
Ah I see you work in a bureau of the German government where fax machines are still the standard of communication. Emails get printed out and faxed over.
We make a singular commit per feature.