Re: Heads Up: cirrus-ci is shutting down June 1st

Peter Eisentraut <peter@eisentraut.org>

From: Peter Eisentraut <peter@eisentraut.org>
To: Nazir Bilal Yavuz <byavuz81@gmail.com>, Andres Freund <andres@anarazel.de>
Cc: Jacob Champion <jacob.champion@enterprisedb.com>, Jelte Fennema-Nio <postgres@jeltef.nl>, Thomas Munro <thomas.munro@gmail.com>, pgsql-hackers@postgresql.org, Zsolt Parragi <zsolt.parragi@percona.com>
Date: 2026-06-04T13:28:46Z
Lists: pgsql-hackers
On 04.06.26 14:13, Nazir Bilal Yavuz wrote:
> Hi,
> 
> On Thu, 4 Jun 2026 at 14:12, Nazir Bilal Yavuz <byavuz81@gmail.com> wrote:
>>
>>>
>>> To make that less confusing, emit a summary whenever we skip running CI, with
>>> a message explaining how to enable CI.  See e.g. the bottom of
>>> https://github.com/anarazel/postgres/actions/runs/26926523027
> 
> I think it would be nice to mention that we need to create a
> 'Repository variable' not an 'Environment variable'.

Yes, it wasn't clear to me what the difference was or which one I should 
choose.  (Your message helped.)




Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. ci: Add GitHub Actions based CI

  2. ci: Remove support for cirrus-ci based CI