Re: What's cooking in git.git (Sep 2023, #02; Tue, 5)

From: Jeff King <peff@peff.net>
Date: Sep 7, 2023, 07:51 UTC
Message-ID: <20230907075148.GB1260471@coredump.intra.peff.net>
In-Reply-To: <xmqqtts8nl67.fsf@gitster.g>

On Tue, Sep 05, 2023 at 06:29:52PM -0700, Junio C Hamano wrote:

Show 9 quoted lines

> * jk/ci-retire-allow-ref (2023-08-30) 2 commits
>   (merged to 'next' on 2023-08-31 at 5fe4861f16)
>  + ci: deprecate ci/config/allow-ref script
>  + ci: allow branch selection through "vars"
> 
>  CI update.
> 
>  Will merge to 'master'.
>  source: <20230830194919.GA1709446@coredump.intra.peff.net>

I think we should pause on this one. While I am excited to see it master (since after all it really does nothing until branches actually incorporate it), the comments from Phillip and Johannes make me think we may be better off re-designing it as a JSON-formatted CI_CONFIG variable.

I don't think we'd have to care about backwards compatibility with CI_BRANCHES that made it into master, since our target audience is Git developers. But it's nicer not to litter failed experiments into the history.

I'll see if I can work up a CI_CONFIG patch to replace it, but in the meantime let's not advance the topic any further.

-Peff