LLVM's tools also appear to be much easier to review, for other people to run etc. I'd suggest at least starting with clang-tidy + scan-build and possibly adding Coverity later. I've found the Coverit

I just noticed this never got committed: https://github.com/tianocore/edk2/blob/master/.gitmodules still shows the old URL.

By the way, I've started getting bounces from Liming's Intel email address.

Yes, that's fine with me.

I'd suggest just using the Gitlab mirror. Unlike cryptomilk.org, Gitlab should be just as reliable as Github and won't introduce another potential failure point.

I'm getting the same error, but with a different packaging of Git: mine's in C:\Program Files\Git\cmd\git.exe . It's version "git version 2.26.2.windows.1". Of course it's possible it's just the same

I was working on a web project recently, and apparently people don't even check email any more! So someone had set up a Slack channel where Github pull requests were posted/linked, and we were suppose

Or at least, that's what Microsoft is betting on! :D Personally, I remain unconvinced about the usability of Github Pull Requests for a project the size of EDK2, but I hope to be proven wrong.

Mike, I'd suggest following what other Github projects do, which I think is to run the CI checks automatically on every change that's made in a pull request - I don't know if it might also be necessar

What's the difference between the CI that runs when a user submits the Pull Request, and the final CI checks that run before the request is merged? Also, I'm wondering why Mergify is being used instea