I wouldn’t do any of that in a CI-only system. If I did, I’d use tools that exist for those jobs that already allow scripting languages.

1. Why wouldn’t you use IaC tools for this? All the majors have Python already.
2. What build or deploy task needs to both create and reference a bug ticket?
3. What build or deploy task needs to do database lookups? Or possibly what task needs those across multiple, independent stages?

I dislike scam money as much as the next person. I do not, however, dislike cryptography. There’s a really good common in the thread about elliptic curve cryptography not having a place on Codeberg anymore and I think that’s valid. I don’t even know if OpenSSL could have a place on Codeberg with this decision. Their nonprofit, their rules. Just not very libre-minded and definitely sets a bad precedent. And before someone tells me Microsoft actively censors GitHub, this isn’t a whataboutism thread. It just reduces my trust in a supposedly open collective.

This is a boilerplate example. I asked for something more than boilerplate. Give me some reasons why I need an incredibly stateful CI engine.

Looking at the examples, you’ve just made a brand new GitHub Actions framework. There’s YAML to wrap everything together and a bunch of Python that’s so declarative it might as well be HCL. Do you have an example that’s a bit more than “do what YAML does only in bash?”