Working on the GitHub Azure migration and for years it's gone so well so far.
OK I have no idea about MSFT SREs, just to be /s.
… in all seriousness, that is hardly proof that Azure isn't having an outage.
its one signal, among others. and in any case, i wasn't trying to prove the parent commenter wrong. i was offering my own signal to the crowd.
I did this in 2019, it avoided so many headaches. CI is better too since there's a nice clean mapping of build -> pod for everything and I can just exec in if something's borked.
I probably only babysit it for 30 minutes per year, including all the upgrades.
10 hours x 10 developers x $70 per hour = $7000, not $70000.
I really hope that didn't send emails out to people.
I was pissed that there weren't any sticks heading to the recycling out of the nodes otherwise I would make myself that chain :)
https://github.com/google-gemini/gemini-cli/issues?q=is%3Ais...
The problem is that it's not enough. The fact that Github uses Git specifically is a technical detail; it could use mercurial equally easily, as Bitbucket used to. Github Actions, OWNERS files, PRs and review tools, issue tracker, wiki are all not Git features.
(I use Fossil 100% offline for personal projects for ref)
I once read someone commenting "Nobody writes code by hand without looking syntax up".
Man, you are just outing yourself as a complete beginner, the field is way deeper than you imagine and it's not even close.
What I am saying is that people learn as much as they need to. They generally don't need to know any more git than is required to interact with github. If anything problematic comes up, they go in with a wrecking ball because they don't truly understand what they are doing. And git has a lot of wrecking balls available.
If you threw them at raw git and asked them to collaborate with someone they'd be up shit creek. They have no idea how SSH or email works for example.
PRs and code review are not. CI/CD is not.
I mean, there are solutions, but none of them seems to have a large enough mindshare and efficiency. (Even though Github's code review tools are pretty spartan.)
They can be. A PR can be made and code review conducted by submitting a patch to a mailing list. That's how the kernel and, I think, git itself is developed.
CI/CD is really a methodology. It just means integrating/deploying stuff as soon as its ready. So you just need maintainers to be able to run the test suite and deploy, which seems like a really basic thing.
I've been looking into having a separate git server that we can commit to and add plain ole git hooks to, and just having it be synced with github as a clone.
Definitely annoying, but I'll try the hot take that, contrary to popular belief, GH is not critical infrastructure - or so I hope.
Please tell me no part of the Ukrainian air defense system depends on a gh action hook.
Need a new secret offensive operation? Create a new JSON file with the coordinates, make a merge request and get Commander approval, merge it, and our new proprietary GitHub action runner will deploy a drone in seconds!
It's also the only reason why I still need IPv4.
nullfish•1h ago
rvz•1h ago
Even self-hosting would have been more stable than sitting on GitHub as predicted more than half a decade ago. [0]
Now there is no 'CEO of GitHub' to contact this time (Satya does not care).
[0] https://news.ycombinator.com/item?id=22867803
someguyiguess•1h ago
ascendantlogic•1h ago
DeepYogurt•13m ago