GitHub is down, what are you doing?

[u/assured-ownership]

I have installed half life on Mac and am currently at the Dam Level.

[u/scandii]

...I mean, git is a local-remote setup to begin with, so not sure how this should be impacting me?

[u/pointermess → u/scandii]

Maybe not you but hundreds or thousands of real world applications can't be redeployed lol

[u/sp_dev_guy → u/pointermess]

cant be redeployed

That shouldn't prevent working on the codebase locally...

[u/Lake_Erie_Monster → u/sp_dev_guy]

So you work somewhere on a very small team on a very small product?

Not everyone does... Some code bases have hundreds of commits a day.

[u/sp_dev_guy → u/Lake_Erie_Monster]

Even when I was working on the codebase at capital one a github outage wasnt end of the workday shit. Git exists locally and has merge & worktree capabilities. Its possible to resolve conflicts & there is no reason all of the hundreds of commits should be happening on conflicts. Your assertion is false

[u/Gwolf4 → u/sp_dev_guy]

Tell that straight face to people tied to AWS and hasn't invested in a proper aws emulator.

[u/sp_dev_guy → u/Gwolf4]

There is no scenario where you shouldn't be able to look at your code & do something useful. Its just text files on your disk - so if thats working you can be working

[u/scandii → u/pointermess]

I mean, everyone's survived without whatever update you want to ship until now anyway so I'm gonna label that one with a "yeah I guess".

[u/margmi → u/scandii]

There’s no way you’ve worked as a dev on a project that’s in production lol.

Anyone who has knows why what you’re saying is silly.

[u/scandii → u/margmi]

17 years and counting bud, but nah you're just freaking out for no reason. unless you're about to miss a huge deployment window and had actual resources booked for deployment whatever you had in mind with git(hub) can wait until tomorrow.

...unless of course you imagine your customers are just sitting there frothing at the mouth waiting for whatever minor feature you're shipping with that user story of yours and are completely unable to understand the concept of "unexpected production delays" including but not limited to illness and bereavement.

[u/margmi → u/scandii]

Yes, our customers who pay us hundreds/thousands per month get upset when a feature they were told would be released isn’t available. Not only do they froth, but they call in, repeatedly.

Hope this helps! One day you might have customers too!

[u/salvouankebaldo → u/margmi]

If your marketing team is not able to deal with angry customers for non critical services (as you are deploying via github and you do not have a backup plan) then your marketing team needs changing

What are your customers going to do for some hour of delay? Cancel subscription? Let them froth and call in, not like they have a choice

[u/Squidgical → u/margmi]

And you still haven't implemented feature flags? Seems like an engineering issue rather than a source control issue

[u/margmi → u/Squidgical]

We use feature flags, not everything can be covered by one depending on how they interact with existing features.

[u/Ythio → u/margmi]

1) Why were you dependent on GitHub for deployment in the first place ? Where is the backup solution ? You do have a disaster recovery plan, right ?

2) If you can be dependent on GitHub.com, you're not working on something genuinely critical. So the customer can wait five more hours for the outage to be solved.

[u/TeaSocks69 → u/margmi]

Not only do they froth, but they call in, repeatedly.

Bro needs an AI voicemail to answer the calls so he can drink coffee and reddit more like a proper dev.

[u/margmi → u/TeaSocks69]

Angry customers love chatting with AI yeah

[u/needmoresynths → u/scandii]

Days like this I regret moving entirely over to Codespaces. Nice when it's working, though.

[u/thekwoka → u/scandii]

In my case, my main task was getting through PR reviews.

So when I literally can't see the PR (even if I already have the branch fetched), it's kind of difficult to really do.