A piece of criticism to all code forges I know: why not run #CI on all commits?

A bad commit is a liability. It will break bisect and make debugging miserable.

#ForgejoActions takes it to the extreme and cancels an already running action when I push another change.

I get it - it's too slow and expensive to test them all when pipelines take minutes to run. But you could just pause the old ones until the newest one is finished!

#testing #forgejo #gitea #gitlab #Codeberg #coding

Follow

@dcz I'm pretty sure gnome's gitlab runs CI on all commits, which can build up quite a big queue of them on frequent commits. But then you can manually cancel those you're not interested in.

Sign in to participate in the conversation
Librem Social

Librem Social is an opt-in public network. Messages are shared under Creative Commons BY-SA 4.0 license terms. Policy.

Stay safe. Please abide by our code of conduct.

(Source code)

image/svg+xml Librem Chat image/svg+xml