This is why I moved my code to self hosted forgejo instance. Private and guarded behind self hosted OIDC instance.

No more worrying about "rate limiting," subscription hell, or random extended outages (ie, github).

If LLM wants access, might implement payment layer and use 402 http status code and redirect them to payment page ;). Wonder how many people just give agents carte blanche physical (credit card) and virtual access

60 requests an hour per IP seems low for a school or office network. A few people browsing issues and source files could use that up quite fast.

I would spend thousands of dollars for gitlab in terms of: 1) better UX for admin panel, I'm not sure what I've enabled and what not. Several buttons do not disable the rest of the settings, leaving me with some doubts (e.g. if I disabled grafana, why is there a setting that talks about where/how I store?) 2) a minimal version of gitlab without all the AI

> You get 429 Too Many Requests with RateLimit-* headers and a Retry-After. Wait the interval it gives you, then retry.

Is there a test endpoint where one can validate the behavior of their ratelimit detection? Basically I do not want to cause excessive load on your servers just to test my implementation.

I forgot a superfluous free tier proof of concept pipeline and it ran every 6 hours for three months before I remembered to shut it off, sorry.

I expect to not be the only one, it certainly drives usage KPIs up and lead to this kind of decisions.

> The requested URL was not found on this server.

Getting that so I do not know exactly what they are doing. From the title I am guessing they are restricting or throttling if downloads exceeds some value.

CI needs to be decentralized, and the agents should run the test and verify the proof. This avoids all those API calls.

does this rate limit also apply to the images which they hosted on registry.gitlab.com? They do have a couple of scanners that we use and we pull it without any authentication

Walk back in 10...9...

429 gang represent