automatic blackening of code might be broken

[sildater]

release 1.3.0 does not seem to be blackened. e.g. the note_features.py module has very wide lines and horizontal lists.

[sildater]

and also doc string length seems to be unaffected by blacken, so we need to check this manually.

[manoskary]

I just realized why it did not work....
I called the workflow to run for PR or push on master not main

[manoskary]

However, I will change the workflow to run only after every push to develop instead, so that the blacken code is first previewed and stays on develop.

[sildater]

Ah, yes that's a good idea!

[manoskary]

The blacken now works on develop and submits a new commit with the blacken code which gains authorship from the person pushing to develop. I will leave this issue open if there are any other remarks about the blacken process, otherwise feel free to close the issue.