Hello, I checked the other PR, the problem there is different there, the branch was found but the Scanner execution failed, with a generic message and it’s our internal issue.
Because we are recently registering a lot of these errors, we are planning to launch an effort in the upcoming days to identify the root causes of multiple failures and implement fixes. I will let you know once we deploy these fixes.
In the meanwhile, I think the best for now is switch to CI-based analysis. If you open your project, go to Administration → Analysis Method, you fill find a list of various supported analysis methods with step by step tutorials on how to execute them. Thanks to that you will prevent your project from being housekept.
The issue with your project is, that the Project Key contains a colon :. GitHub doesn’t allow to use a colon in their repository names, they automatically replace it with a dash - and we use the repository name as a default Project Key. This means that you probably updated the Project Key manually? To quickly fix your problem, please go to your Project → Administration → Update Key and choose a project key which doesn’t contain a colon. You can just simply replace it by a dash. After that your Automatic Analysis should work.
Thanks for the update. I changed the key and moved back to automatic analysis and it seems to be up and running again! Great news and thanks for you help!
It’s great to hear that the Automatic Analysis is up and running again for you. We also discovered the bug for PR analysis coming from forked repositories. The fix has been implemented and released in production. Thanks for pointing out this issue.