Cassandra is only carbon nowHot take, as someone who definitely encouraged a lot of folks to start using CI: your project may not actually benefit from CI. That's OK.
If it's a small, hobby thing, CI is overkill. Set up a build/test script, make sure to run it before you push changes, and you're good.
CI has become a huge kind of lock-in, in part because it provides a lot of value — but it's worth asking whether you make use of that value or not.
Cassandra is only carbon nowIf it makes it easier to leave GitHub, it's especially worth considering whether CI is actually useful to you. There's a good chance it is! But not a 100%, either.
Cassandra is only carbon nowThings that have replaced CI for me now that I'm coding to make my own life better, rather than as a profession: just, direnv, nix shell, docker, uv, etc.
All extremely different tools, but have in common that they're things that allow me to run things in a folder without worrying about what all else I may have elsewhere. That's all I really need, not full reproducibility, not CI, just separability between side projects.
Cassandra is only carbon nowAnyway, none of the above is "don't use CI," it's "ask yourself if you actually need CI, and be prepared for the answer to either be yes or no, depending on what you're trying to do."
narF 😵
✌
️@xgranade@wandering.shop What is CI in this context? From the replies, it seems like a Github thing?