Horton
Menu

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

Jelte Fennema <postgres@jeltef.nl>

View thread
From: Jelte Fennema-Nio <postgres@jeltef.nl>
To: Andres Freund <andres@anarazel.de>
Cc: Peter Eisentraut <peter@eisentraut.org>, Nazir Bilal Yavuz <byavuz81@gmail.com>, Jacob Champion <jacob.champion@enterprisedb.com>, Thomas Munro <thomas.munro@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>, Zsolt Parragi <zsolt.parragi@percona.com>
Date: 2026-06-02T19:06:39Z
Lists: pgsql-hackers 
On Tue, Jun 2, 2026, 20:43 Andres Freund <andres@anarazel.de> wrote:

> From what I can tell the workflow of plenty folks during their own
> development
> is to open PRs in their own repo.  I don't really see a downside to also
> running on PRs, so I'm inclined to do so. Won't hurt us...
>

Generally you should do one or the other. Otherwise all jobs will be run
twice when you push to a branch that is linked to a PR. So I'd say, only do
push

>

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