```
This git endpoint is seeing a high influx of requests for this repository, to preserve the availability of Codeberg your search request will not be processed. Sorry for the inconvenience and please try again later.
```
Critical: fix: prevent template expansion from interfering with git repo initialization. When generating a new repository from a template repository, Forgejo clones the template repository, removes the .git folder, performs variable template expansion on files listed in .forgejo/template, and initializes a new git repository. During this process, variable template expansion could be misused in order to create a new .git folder, which git would adopt and incorporate during its initialization of a new git repository. A malicious template repository could be used to read arbitrary data from the Forgejo host, and to execute arbitrary processes on the Forgejo host, as a remote code execution attack. To address this issue, after variable expansion is completed, any existing .git folder is removed from the directory before the git repository is initialized.
Gitlab has the benefit of having very little traffic, both free and paid. Their limits are still way above the current usage so less likely to be an issue
Worth mentioning GitLab's paid enterprise offering are more expensive than GitHub's, on a per-seat basis.
Lots of companies moved because it was cheap, but it's not anymore. Ironic that companies might choose to migrate to them now for stability, rather than price.
GitLab has its own problems. It might be somewhat more available than GitHub lately, but it too is not immune to incidents, particularly involving workflow dispatch and managed runner availability.
Plus the UX isn’t nearly as good. Sometimes it feels downright clunky in comparison.
Great read - I'm glad they realize there's work ahead but what I'm missing is:
* Paid customers: we know you pay us often a ton of money, and we burn your month on actions during these outages - we'll refund you for the days we spent your money and gave you no value.
* Paid customer: We know you put your trust in us, so we'll ensure we have a separate pool of capacity to ensure we can keep that trust.
* Paid customer: we'll proactively refund you when we miss our SLA.
What I read from this is:
* Scaling is hard, we don't have enough capacity
* We give away a shitton of compute for free
* I have to talk about Azure not being a steaming pile of poop, otherwise my bonus will get tweaked downward in the next comp cycle.
Notice there's nothing about paid customers, I'll add in what they are missing:
Paid customers: Go F*ck yourself, you don't pays us enough to be an interesting line item compared to windows server.
This. I own a small company with 5 people. I pay Github $250/m. I'm sorry but the narrative of, "look at this burden we have, it's hard to take care of all of this code!" is pretty insulting when I'm paying $50 per person per month to host code and run CI pipelines. If they do not want my money, I'll find a company who does.
except when you are paying for their enterprise edition - and they make no distinction between paying customers (quite a bit actually once you add in actions costs + their other addons, it's quite a bit of money) and their free tier full of AI slop PRs on rando projects.
As someone who pays github, I'm super annoyed at the downtime and still I'm getting charged for actions running that all fail from their lack of concern for their enterprise customers.
Having some independent pools of capacity for paying vs. free customers isn't rocket science, it's basic competence (or care). I'm quite sure their are competent people remaining at GitHub (although I hear most of their original folks have left, and the 2nd tier of folks who joined from microsoft seem lackluster at best). I chalk this up to lack of care, or hubris, or both.
Oh I agree that the outages are unacceptable regardless of their “social media origin”.
I also don’t buy their excuse that it’s due to increased loads due to AI. If that were the case then we’d see more patterns to the outages. But instead it affects all GitHub systems but at different times. It feels more like a problem with their orchestration layer than capacity issues.
I recently had to rebuild a jira frontend from scratch just so a single jira tab didn't take down my 8gb MacBook. Support only the subset of features I actually use and it's great. Makes me hate jira even more.
I was happy when they got rid of the virtual keyboard you had to type your password onto, such a pain since you also couldn't paste into the password field to autocomplete from a password manager.
Had to constantly popup Chrome DevTools and "fix" the dom element to let paste work.
If they let you paste your password, you might use a long, randomly generated password stored in a password manager, instead of choosing a short, easy-to-type password and using the same one everywhere.
Any mirror?
reply