I understand it’s a joke, but really isnt the entire point of git is to be able to work locally as much as you want without affecting the remote repo and vice versa
You should be able to replicate at least some of that locally. If you can’t work with GitHub down for a couple of hours, then it’s a poorly set up project.
Git allows me to write code as much as I want. But GitHub does more than just Git. If you don’t remember the details of the next task you need to work on and GitHub is down, that’s a problem. As a senior I spend a lot of time reviewing PRs. That’s considerably harder when GitHub is down.
I mean there are tons of options in that space so if it’s an issue that is sorta on your business to have evaluated their dependency.
We work on an internal gitlab instance that has had 100 percent up time for like 2 years. It doesn’t even have to be gitlab, there’s gitea and like 10 other options.
I personally think that the industry has moved so far in the direction of cloud and saas that it’s lost a lot of valuable skills and made them dependent on too much externally.
I understand it’s a joke, but really isnt the entire point of git is to be able to work locally as much as you want without affecting the remote repo and vice versa
For some reason tons of developers moved that amazing concept to depend as much on Microsoft cloud as possible for their workflows.
GitHub has actions etc. a lot of people don’t build locally. They push to GitHub and it builds, tests, deployed, does checks etc
You should be able to replicate at least some of that locally. If you can’t work with GitHub down for a couple of hours, then it’s a poorly set up project.
Tell me you don’t actually code enterprise without telling me you don’t actually code enterprise.
Nah. If your entire dev team has to be on pause when github is down, you’re doing it wrong. Especially enterprise.
Sorry but that is just the reality these days. Instead of having local «it works on my computer» setups you have one place that builds
Off code you could run your own gitlab or whatever but it’s just cheaper and more efficient to buy a sass solution
You should have both. Having your entire dev team unable to work when one service is down is absurd.
Welcome to the world of SaaS I guess? It’s very standard. I mean GitHub used to have better uptime than you could achieve on your own.
Git allows me to write code as much as I want. But GitHub does more than just Git. If you don’t remember the details of the next task you need to work on and GitHub is down, that’s a problem. As a senior I spend a lot of time reviewing PRs. That’s considerably harder when GitHub is down.
I mean there are tons of options in that space so if it’s an issue that is sorta on your business to have evaluated their dependency.
We work on an internal gitlab instance that has had 100 percent up time for like 2 years. It doesn’t even have to be gitlab, there’s gitea and like 10 other options.
I personally think that the industry has moved so far in the direction of cloud and saas that it’s lost a lot of valuable skills and made them dependent on too much externally.
It’s possible to design your devex to require an unreliable SAAS vendor for even basic tasks! If you try hard enough you can logjam your entire team!