News for hackers. Stuff that matters.
Re:Securing a GitHub repo is a ton of work by stoplying1 on Friday October 21, 2022 @08:03PM (#33294245)
It's called CI. Gasp.

You know, the thing you need if you're stuck in 2000's eea deployments. Or the thing you need if you're deploying VMs. Or the thing you need if you're deploying containers. "You know*, the thing you need if you give a shit about your product.

Oh wait, what, you're running a live service, connected to public internet? And you somehow think "lol gotcha rust updates are a thing" is an own? Once again, y'all keep tattling on yourselves!! While acting so smug, I (really don't) need some of that ignorant confidence! *Please!!!!* Feel free to link us to your running live services that you apparently can't run CI/CD for. Its totes fine, right?

Re:Securing a GitHub repo is a ton of work by bombolo on Saturday October 22, 2022 @05:55AM (#33296867)
It is a well known fact. Please don't get angry at me.

> It's called CI

So do you have a CI about every single binary (maybe closed source) that you run?

I don't have a CI for bash, cat, ls, stat, ln, bc, grep… I know they are well maintained and get updates.

If I need a CI as a end user… that thing is already obviously garbage.

> Oh wait, what, you're running a live service, connected to public internet? And you somehow think "lol gotcha rust updates are a thing" is an own? Once again, y'all keep tattling on yourselves!! While acting so smug, I (really don't) need some of that ignorant confidence! Please!!!! Feel free to link us to your running live services that you apparently can't run CI/CD for. Its totes fine, right?

Ping me when you are done making random rageful assumptions thanks.