Re: how to manage Cirrus on personal repository

From: Melanie Plageman <melanieplageman(at)gmail(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: how to manage Cirrus on personal repository
Date: 2023-09-29 13:38:56
Message-ID: CAAKRu_YUN3m_2pHatkR4QWwe6TTGvz4-DRG1OgMwO5+mFC3n-g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 29, 2023 at 7:11 AM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>
> > On 29 Sep 2023, at 11:13, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
>
> > Does anyone have an idea how to manage this better? Is there maybe a way to globally set "only trigger manually", or could we make one?
>
> On my personal repo I only build via doing pull-requests, such that I can
> control when and what is built and rate-limit myself that way. Using the
> Github CLI client it's quite easy to script "push-and-build". Not sure if it's
> better, it's just what I got used to from doing personal CI on Github before we
> had Cirrus support in the tree.

It is not a global configuration solution, but I just add an empty
ci-os-only: tag to my commit messages so it doesn't trigger CI.
I'm sure this is not what you are looking for, though

- Melanie

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2023-09-29 13:47:43 Re: Eager page freeze criteria clarification
Previous Message Ерохин Денис Владимирович 2023-09-29 13:36:27 Fix receiving large legal tsvector from binary format