Re: js/ci-coverity, was Re: What's cooking in git.git (Oct 2023, #02; Wed, 4)

From: Junio C Hamano <gitster@pobox.com>
Date: Oct 5, 2023, 18:44 UTC
Message-ID: <xmqqh6n4j4ei.fsf@gitster.g>
In-Reply-To: <20231005170859.GB975921@coredump.intra.peff.net>

Jeff King <peff@peff.net> writes:

Show 19 quoted lines

> On Wed, Oct 04, 2023 at 04:45:34PM -0700, Junio C Hamano wrote:
>
>> * js/ci-coverity (2023-09-25) 7 commits
>>  - SQUASH???
>>  - coverity: detect and report when the token or project is incorrect
>>  - coverity: allow running on macOS
>>  - coverity: support building on Windows
>>  - coverity: allow overriding the Coverity project
>>  - coverity: cache the Coverity Build Tool
>>  - ci: add a GitHub workflow to submit Coverity scans
>> 
>>  GitHub CI workflow has learned to trigger Coverity check.
>> 
>>  Looking good.
>>  source: <pull.1588.v2.git.1695642662.gitgitgadget@gmail.com>
>
> I think that has been sitting at "Looking good" for a few iterations.
> IMHO it is ready to progress, with the SQUASH applied on the final
> patch.

Ah, yes, unless I use some magic phrase (like "Will merge to" or "Expecting") there in the report, entries tend to be left in the noise. Thanks for noticing and pinging. Very much appreciated.