llvm dev - Jun 2021 - Coverity Scan Needs to be Updated after GitHub Migration

As a reminder, the Coverity scan of the llvm project,
https://scan.coverity.com/projects/llvm is still pulling from the old subversion
repository. It needs to be updated to https://github.com/llvm/llvm-project.

Whoever setup the original account, needs to change this. Or someone with admin
permissions on github needs to create a new account? Who would I talk to about
this?

I doubt anyone on this mailing list has any control over the Coverity scan. 
I'd suggest emailing Coverity; it looks like the address is scan-admin at
coverity.com .

-Eli

-----Original Message-----
From: llvm-dev <llvm-dev-bounces at lists.llvm.org> On Behalf Of Luke
Benes via llvm-dev
Sent: Wednesday, June 2, 2021 12:14 PM
To: llvm-dev at lists.llvm.org
Subject: [EXT] Re: [llvm-dev] Coverity Scan Needs to be Updated after GitHub
Migration

As a reminder, the Coverity scan of the llvm project,
https://scan.coverity.com/projects/llvm is still pulling from the old subversion
repository. It needs to be updated to https://github.com/llvm/llvm-project.

Whoever setup the original account, needs to change this. Or someone with admin
permissions on github needs to create a new account? Who would I talk to about
this?




_______________________________________________
LLVM Developers mailing list
llvm-dev at lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

> * it was often regressing
If there is interest, I'd be willing to help with the cov-build,
> * afaik, nobody but me was paying attention to newly detected defects (if I
am wrong, please let me know and I can have a look).
In my experience, a weekly report of new defects helps keep engagement up and
issues down. Here is an example:

http://document-foundation-mail-archive.969070.n3.nabble.com/New-Defects-reported-by-Coverity-Scan-for-LibreOffice-td4301033.html

Would a weekly scan report be welcome here?