PSA - Please be careful not to create addition Codacy instances for the saros project

[Tobias Bouschen]

Hi all,

we have recently moved to using Codacy as our CI tool for static code
analysis. We are still experimenting on how to configure it properly
(which rules to keep and how to best integrate it into GitHub), so none
of the rules are currently being enforced (meaning violations currently
should not cause your build to fail).

But, due to the somewhat confusing Codacy UI design, it now happened
multiple times that a developer accidentally created an addition Codacy
instance for the central Saros project. The problem is that each
developer with write access can currently create such instances. These
instances analyze the current PRs by default and also automatically
report the results to GitHub. As these new instances are not configured
properly, this leads to many PR builds being marked as failed (as the
Codacy build "fails" when it finds issues).

So please be careful when signing up for Codacy. Directly after signing
up, Codacy will show the site to "select projects for review" which
contains a list of all of your GitHub project. Clicking on one of them
will create a Codacy instance for the project. (From what I have grasped
from the interface, it sadly does not seem to be possible to abort the
setup process once it has been started.)

If you have accidentally created such an additional Codacy instance,
please delete as soon as possible.

We are also currently trying to figure our if there is a way to avoid
this issue by restricting who can set up Codacy Instances for the saros
project.

Best regards,
Tobias