301–310 of 425 posts
Earlier quoted context omitted.
Issues, CI, and downloads for built binaries aren't part of vanilla Git. CI in particular can be hard if you make a multi-platform project and don't want to have to buy a new mac every few years.
Probably Worth taking an honest look at whether your CI could just be an SQS queue and a Mac mini running under your desk though
i was right ... https://medium.com/@patrick.szymkowiak/github-is-falling-apa...
coincidence I think not!
Earlier quoted context omitted.
Is there any reason why Github needs 99.99% uptime? You can continue working with your local repo.
As an example, Go build could fail anywhere if a dependency module from Github is not available.
Earlier quoted context omitted.
Yeah, I'm literally looking at GitLab's "Migrate from GitHub" page on their docs site right now. If there's a way to import issues and projects I could be sold.
Maybe it's be reasonable to script using the glab and gh clis? I've never tried anything like that, but I regularly use the glab cli and it's pretty comprehensive.
Earlier quoted context omitted.
Lots of teams embraced actions to run their CI/CD, and GitHub reviews as part of their merge process. And copilot. Basically their SOC2 (or whatever) says they have to use GitHub. I’m guessing they’re regretting it.
> Basically their SOC2 (or whatever) says they have to use GitHub Our SOC2 doesn't specify GitHub by name, but it does require we maintain a record of each PR having been reviewed. I guess in extremis we could email each other patch diffs, and CC the guy responsible for the audit process with the approval...
You can literally watch GitHub explode bit by bit. Take a look at the GitHub Status History; it's hilarious: https://www.githubstatus.com/history .
I think this will continue to happen until they finish migrating to Azure
Earlier quoted context omitted.
Is there any reason why Github needs 99.99% uptime? You can continue working with your local repo.
I'm a firm believer that almost nothing except public services needs that kind of uptime... We've introduced ridiculous amounts of complexity to our infra to achieve this and we've contributed to the increasing costs of both services and development itself (the barrier of entry for current juniors is insane compared to what I've had to deal with in my early 20s).
All kinds of companies lose millions of dollars of revenue per day if not hour if their sites are not stable.... apple, amazon, google, Shopify, uber, etc etc.
Those companies have decided the extra complexity is worth the reliability.
Even if you're operating a tech company that doesn't need to have that kind of uptime, your developers probably need those services to be productive, and you don't want them just sitting there either.