Hi,
On 2026-06-03 19:36:29 -0400, Andres Freund wrote:
> On 2026-06-03 16:03:20 -0700, Jacob Champion wrote:
> > On Wed, Jun 3, 2026 at 12:57 PM Andres Freund <andres@anarazel.de> wrote:
> > > On 2026-06-03 11:12:43 -0700, Jacob Champion wrote:
> > > > Are we certain that GitHub isn't going to opt them all into
> > > > test-every-stable-commit-and-PR on their next sync?
> > >
> > > It'd not test every stable commit, just the ones separately pushed, no?
> >
> > Ah. Slightly embarrassing: I misunderstood the Sync Fork functionality
> > in GitHub, which I'd never actually used. It's a one-time
> > synchronization, not a permanent "keep this up to date" toggle, so the
> > situation's not as alarmingly carbon-intensive as I made it sound.
> >
> > So yes, just every push. I don't know if the Sync Fork button acts as
> > a push trigger as well.
>
> Jacob and I just tested this with a test account that I had around. A new
> fork starts out with disabled workflows. But forking before this and then
> resyncing / pulling remaining changes, does lead to the workflow being
> disabled.
Err, I typo'd, thinko'd the last disabled, that should have been "enabled",
unfortunately.
Greetings,
Andres Freund
