It is not even the end of the month and the outages are increasing every month and it is now chronically unreliable. Seriously, we have given GitHub more than 3 years to improve and it clearly isn't working. That is plenty of time.
At this point, you might as well self-host like the rest of the open source projects out there, since GitHub is falling apart every week and it seems to be more reliable to self-host than to sit on GitHub, go all in and tolerate these outages every calendar month.
It seems like GitHub is down at least once a month now, but more like weekly on average.
Seriously now: these instabilities happened a lot on the past weeks. I wonder what's going on there.
This kind of GH outage is actually pretty rare in my experience in that basically every kind of write operation looks down.: basic git operations from the command line, actions, logins, etc.
Github being down for a bit shouldn't disrupt your work flow
European working hours == Github maintenance window?
F that.
Who would have thought software could be such an adrenaline rush. Move over Alex Honnold!
I also don't just mean outages like this... it's clear that Microsoft GitHub has been cramming a bunch of new stuff into the UI and not really treating it with care. I notice very amateur UI bugs, misalignment, bad spacing, overlapping elements, etc. all the time now. It was clear that old GitHub passed through a professional designer's eye quite carefully (or maybe just a developer with extreme attention to detail).
Seriously. Example: the "merge pull requests" button. If your repository requires linear history and the current type of merge is unavailable, the entire UI element turns grey instead of green. It looks like you can't use the button at all, but the dropdown arrow still works to select a valid type of merge (which then turns the entire element green).
It's a small thing, but it causes confusion by making it appear that the change cannot be merged, and it makes you wonder how much testing they do.
These little things keep piling up as they focus on shiny new features which rarely work correctly at launch (looking at you, code search...)
Please, GH product managers. Take a break from breakneck new features, and give your devs time to clean up and do some preventative maintenance.
+1
The inconsistencies aren't deal breakers - github still has a very pleasant UI overall - but they do makethe website feel more and more unpolished each day
Bonus points for a local HTTP service that provides an optional GitHub-like experience in the browser, with comments/ branch reviews/etc. federated through emailed messages (and represented as commits on meta-repos).
With that data model, the primary remaining challenge would be setting up repos on a new machine -- perhaps BitTorrent could help :)
I quickly pointed about a major outage affecting Gitlabs shared runners which prevented us from deploying a hot fix (we worked around it, but was a ton of stress and extra work).
I assume most people don't even pay for it with their public and private non-work repos. Github has been a major supporter of OpenSource projects and while their uptime could use some help, everyone is struggling right now with RIFs and fewer resources.
That's just my $0.02
Human agency tends to normalize on the brands with biggest marketing budget who collude with politicians to create a moat for themselves. There’s your real problem.
Of course none of the propaganda research that made its way from military after world wars to corporate advertising and marketing college programs has any influence on lizard brains. No sir.*
* this comment is paid placement
So? That's entirely self inflicted.
Another one: IIRC, for some reason, there is no "fork" button on mobile UI. You have to go to desktop mode to click the fork button.
That's kind of how Microsoft works in general. Their products expand to have as many features as they can cram in. Word and Excel are probably the quintessential examples, where only a tiny fraction of users care about a feature, but they are passionate about it.
"RIF" is US jargon; you can see that ~0% of worldwide Google usage outside of North America for "RIF" is "reduction in force" [https://trends.google.com/trends/explore?date=now%201-d&q=%2...]. A tiny amount (<<2%) of usage in UK, Scandinavia, Poland, Australia (possibly mainly from US multinationals).
More corroboration: https://en.wikipedia.org/wiki/RIF
There is zero reason to adopt managementspeak jargon, or its 2022 neologisms "impacted"/"affected"/"displaced". Just say "layoff" (n) / "laid off" (v), already.
In the very unlikely event [in tech] you actually needed to say "temporary layoff", you can easily say "temporary layoff".
The language was working fine for decades and there's no reason to pander to management euphemisms. It harms clarity.