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

From: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
Subject: Re: Heads Up: cirrus-ci is shutting down June 1st
Date: 2026-06-02 19:06:39
Message-ID: CAGECzQRKcLLzmK6PSHxXm8qfD7c6HsYVmtT7qLW2ve2=YR+WEQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 2, 2026, 20:43 Andres Freund <andres(at)anarazel(dot)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

>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2026-06-02 19:12:16 Re: Heads Up: cirrus-ci is shutting down June 1st
Previous Message Andrew Dunstan 2026-06-02 19:03:57 Re: BackgroundPsql swallowing errors on windows