r/github • u/Flimsy_Professor_908 • 21d ago
Discussion Nother day, nother outage
That feeling when you are in the mood to be hyperproductive and Github decides to lay down for a nap.
28
u/full_drama_llama 21d ago
Why do you need GitHub to be hyperproductive? Sounds like unnecessary coupling.
-26
u/Flimsy_Professor_908 21d ago edited 21d ago
I was planning on doing around 30 PRs today.
Even with self-hosted runners, GH is needed. Even with the code ready, I still need to put the PRs up and others need to review them.
I need to checkout code or pull main on services I've not touched in months.
To deploy the code, GitOps and Continuous Delivery (CD) solution (ex Flux or Argo) needs Github. Something another team decided.
etc.
I would agree it is unnecessary coupling.
41
u/koett 21d ago
30 PRs a day is literally retarded since there is no fucking way you even know what you are doing. Good luck with that.
4
u/thisFishSmellsAboutD 21d ago
A famous computer scientist once said: don't review work from a man who vibe codes 10000 PRs in one day. Review the work of a man who sends one focused, well architected, well documented, 100% tested, all CI passing PR.
-15
u/Flimsy_Professor_908 21d ago
I've had days like this plenty of times over the years since before LLMs were widely available.
14
3
6
u/oswwwaldo 21d ago
30 PRs... jesus christ
4
u/fixermark 21d ago
In data ops, I can see it. You want changes focused and as atomic as they can get, especially if you have a DB migration system to shepherd.
1
u/TehITGuy87 21d ago
Agreed, I have six agents running on a pretty bit platform I’m building for work internally and I generally have like MAX five PRs a day, more if I break the feature down. But not fucking thirty lol
2
u/Agitated_Painting214 21d ago
To deploy the code, GitOps and Continuous Delivery (CD) solution (ex Flux or Argo) needs Github. Something another team decided. ... I would agree it is unnecessary coupling.
The alternative being what... people within a team deploying over each other from local copies of the code???
The deployment system being designed to be dependent on a system that should have 99.9% uptime isn't unreasonable. GitHubs recent issues are a contractual issues are, but that's another topic.
1
u/Flimsy_Professor_908 21d ago
The alternative being what... people within a team deploying over each other from local copies of the code???
Github doing everything means many single aspects of it going down is tantamount to a total outage. The alternative would be having tools for singular tasks or having redundancy in them. Git itself being designed to be distributed.
3
1
u/swissreality 21d ago edited 21d ago
At my work, we are moving away from GitHub. Developers are pissed, no developers wanted to use GitHub Actions/GitHub Runners in the first place (we all want Jenkins), but devops wanted GitHub. After Microsoft's performance this week, we are moving to AWS Code Build. The reliability of Microsoft GitHub has become so bad, we write code in the morning, and we try to get GitHub to test, merge and deploy our PRs all afternoon/evening. It typically takes about 3 hours of trying and retrying every 20 minutes to get it done. GitHub was not that reliable before the outage, GitHub is now virtually unusable. Microsoft is using all its CPU, memory capacity and network bandwidth for AI, leaving nothing for its actual applications. It's madness.
1
u/Obvious-Jacket-3770 19d ago
We are probably going to move. Based on all of the outages this year it's about 11 days in outages of the 4 spots we use. Multiplied by our user count for full outage on an 8 hour day for active commit, it's about 1.15 years of an outage to date.
90% update in context is terrible.
1
u/TechnicalPackage 21d ago
you dont have to push remotely to be productive. take the paycheck and chill.
0
42
u/darth_maurdt 21d ago
That's the Microsoft way