You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I usually mergetest a lot of PRs at once, then merge them one by one as I test them.
In current system, this results in a whole lot of tiny, empty releases. This is obviously not good.
I could try discipline and not merge until I test a whole batch, but that sounds tedious and prone to mistakes.
I could also try merging my mergetesting branch onto main and pushing that, but it only works if all of the tested PRs are ready.
Ideally, there would be a way to:
Delay releases to something like 1 per day, if something was merged this day
Automatically delete empty releases and append their changelog to the first complete release
Detect partly-cancelled releases (cancelled when only some of the builds completed) and treat them like empty ones
The text was updated successfully, but these errors were encountered:
I never seen before anyone complaned. Probably people get used to unstable releases for Cataclysm.
Obvsily it is somewhat messy, but it is not "true" releases - it is experimental releases after all.
Having release strategy will solve that. I mean normal release strategy with master, dev, version tags e.t.c.
nanohard actually pointed to that: #673
I usually mergetest a lot of PRs at once, then merge them one by one as I test them.
In current system, this results in a whole lot of tiny, empty releases. This is obviously not good.
I could try discipline and not merge until I test a whole batch, but that sounds tedious and prone to mistakes.
I could also try merging my mergetesting branch onto main and pushing that, but it only works if all of the tested PRs are ready.
Ideally, there would be a way to:
The text was updated successfully, but these errors were encountered: