I've been using ConcourseCI because another team manages it and it is integrates with Hashicorp vault.
It's good. The big advantage is I don't have to deal with maintaining it.
The downside is their story on GitHub integration is kind of crummy, you have to create your own web hooks because our ConcourseCI instance is too busy for poll based resource checks.
I'm not happy that it's YAML but it's become ubiquitous. Sure, there are lots of other formats that others have mentioned, but I'm sorry most of them are positioned as "it's better than YAML!" and the fact that everyone is mentioning YAML, even if it's about the things it does wrong (and boy does it do things wrong) still means that YAML is on everyone's mind.
On the foreign policy front, he's just not following US imperialist policy so the US media is hitting him with this piece to prevent the Overton window from shifting.
Like, he's not a good candidate and it's heartbreaking when the worst person you know makes a couple of good points that make the neoliberal imperialists go nuts, but here we are
It's a shame because for better or worse, it was a feature developed due to the worst behavior online. Like, people got treated really badly, enough that Twitter made it in the first place, and Musk is like "nah, no institutional memory, no reason to have it"
Your QA team should be building automated regression tests and automating their tests so that they can be run locally as part of the development cycle or as a job in your CI system.
That would decouple this incredibly tight release cycle that you currently have
MSYS2 has support for GTK, since I think the windows installer for git (which uses MSYS2) would include GUI tools built with GTK