Summary & why

Currently when Black encounters a SyntaxError while parsing during its AST safety check, it tries older versions of Python to see if it will parse then under its grammar (i.e. the syntax - which is an oversimplification but generally words). In other words, if you have a file that is valid Python 2.7 code and are running on Python 3.8, Black will first try will try Python 3.8

Related with nunomaduro/phpinsights#23 will be a great idea to allow set all commands parameters from config/insights.php when is used with php artisan insights.

Maybe something like:

'parameters' => '--format=json -d memo

The fix for #3307 was done for GitRepository only. This bug tracks the rest of the repositories.

Since the default output is meant to be human-readable, would it make sense to add thousands separators to make the output more easily readable?

This is to help people that for whatever reason don't want to go through the effort of changing it manually every time.

Default levels of understanding and thoroughness for both positive (review)and negative(flag) could also be configurable in the user-config file.

Please add C# syntax support.

It would be cool to add Google Translate support, because most likely Google Translate is better than Microsoft Translate.

And maybe it would be good idea to use Google Apps Script, because it has a free unlimited Google Translate. Here is an [example article](https://techstreams.github.io/2016/01/07/translation-automation-with-wor