if you refresh enough times it'll tell you about a ".chefignore" file which is also not the correct name. At least that name might have been correct once?

I swear, the people who rely on these LLM answers daily must either not care that they're full of errors or just really have a hard time noticing

the correct info was right there. You can just create a file called "chefignore" and it does what you want but sure let's make up a different file that no website on the internet uses

cooooool google lie bot invented a ".kitchenignore" file WHICH IS NOT A THING

@Nickiquote hopefully it's not windy that day they need to, uh, defend stuff

this is genuinely SUCH A RECURRING pattern working in IT. People do shit that is bad and then they blame the infra when their bad shit is bad

well, I found out they have 5 test suites and they run them one at a time inside a single job. So there's no concurrency to make up for all the waiting the tests do.. And they only run on a single CI runner because it's all one job.

So his "I have to wait 60 minutes to release one small change" complaint could easily be cut down to 1/3rd the time by changing his CI definitions and doing NOTHING to the underlying infrastructure

A colleague has had a lot of problems with our gitlab CI running too slowly. I had him send a link over of a particularly bad instance where it takes 30 min to make the MR and then 30 more to release the changes when the pipeline runs on main...

@bettina flixbus til Oslo er desværre den slags oplevelse hvor jeg plejer at tage turen om natten så jeg kan sove det meste af tiden. Ville være helt fantastisk hvis tog til oslo ikke krævede 2-3 skift.

@reynir it works

@joepie91 @tobi cool, if only I could get it to work