Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This seems to be the third or so day in the past week I've had issues with GitHub around this time in the morning. They've typically been really good. I'm a bit surprised there hasn't been more talk about it on HN.



They seem to be doing heavy work on it. Now on Mobile you can't see repos in "Desktop Mode" which is unfortunate. I have to tell my browser to pretend to be in desktop mode. Plus the regex post from the other day seems to imply they are working on new things when somebody from GH replied in said thread. I don't mind improvements, but don't break production guys...


They also changed the "Group Membership" dialog to be paginated when you add a new person to an organization. We have over 200 groups so now I have to page through for ever new hire we add. There's not even a search option.

I'm sure the pagination might better for performance, but it's terrible UI.


They may have missed that one, because at the same time they introduced both pagination and search to the repository membership page, and boy did that help us on one of our repos with a few hundred direct collaborators, by the end we could only manage access through the API because the page didn't even load most of the time.


I see why web pages need pagination so the server or browser doesn't OOM, but there really ought to be 10000 entries per page, not 25 that most sites seem to like.

Ctrl+F on a list of 10000 entries is far easier than clicking through 400 ajaxy pages and trying to figure out some custom and buggy filtering system that probably doesn't allow regex.

Past 10000 records most sites probably ought to just let you export in something bigquery compatible anyway - Regular Joe isn't going to have more than 10000 of anything, and anyone who does can learn how to use proper data tools.


> there really ought to be 10000 entries per page

Did you miss the part where I noted Github’s lists fail to load (let alone render) long before that point?


They really need beta.github.com to let people test changes that are not yet defacto. A uservoice type of thing, and the ability for people to join. I love to beta test and give feedback. Microsoft has used uservoice in the past, as has Sulake and other companies I've beta tested for (as a customer).

Edit:

Realized *.github.com takes you to your .github.io sites.


> Now on Mobile you can't see repos in "Desktop Mode" which is unfortunate.

Wait, what? On iOS Safari I can only see repos in desktop mode now (except the issue tracker which is responsive anyway). Which is a good thing. Not sure why you have the exact opposite experience?

(I do vaguely recall being asked if I would prefer desktop mode on my phone a while back, and I said yes.)


I think it sets a cookie or similar to save this.


[flagged]


Intentions are meaningless. If you're providing a service, (especially charging money for said service), you can't break it because "you're hard at work".


>you can't break it because "you're hard at work"

Apparently you can...because it is broken.

A few days of degraded service is frustrating, but their up-time has bought them a lot of credit in my book - especially considering what they do.

This is the real world. No service is magically infallible.


> Intentions are meaningless

Are you a robot? Have some humanity...


GitHub is not a human being, it's a company.


A lot of people have patience on day one, but this is the third or so day now this has happened. It’s understandable there are ruffled feathers.


Yeah... once every few weeks is one thing. Once a day is getting really annoying.


Yea, I'm surprised I didn't see anything from the outage yesterday.


Maybe they can’t post it because it doesn’t work /s


Still miles better than BitBucket.


When was the last time BitBucket had an outage? Personally I don't see a lot of difference between the two platforms; or GitLab (my primary now). Github probably has the best UI, but Gitlab's has gotten a lot better; and there are always self hosted solutions like Gogs.


> When was the last time BitBucket had an outage?

I've been doing on-going client work for someone using BitBucket and for weeks it feels like every other day has an outage related to their pipelines (CI) feature (the thing I happen to be working on).

It was constant banners about service disruption. There's a lot of UI outage related issues too, like the pipelines page starting to show a new build but never updating any of the progress until you reload the page -- which sounds like some type of API outage somewhere. I'm not sure if that gets reported as an outage but it makes using the platform not fun.


I'm pleased I don't have to deal with BitBucket any more, but back a year or two it felt like it had an outage that impacted work at least once every six months. Sure that might not sound like much, but it was always a pain.

Plus of course the service was so damn slow that using it was a daily pain.


There's a yellow banner (that you can't even close) shown every few weeks, and it's usually related to the Pipelines being down, again. That often results in degrading functionality in other parts of the project too. And it's still slow as molasses. I wish I'll never have to use Bitbucket again, in the future.


How much data does BitBucket have to process on a daily basis compared to GitHub, or GitLab?

I imagine that there are stability issues that any provider will have to deal with as they scale to account for the masses.


Github's diffs are pretty much instantaneous, Bitbucket just gives up, "now that's a lot of code!". No, it was a one line change actually.


Github will bail on large diffs, too.


I've also much preferred GitLab's GUI. It seemed to be much cleaner and smoother than Githubs (not to mention the much better named Merge Request).


Sure, but not better than Gitlab.


Do you use Gitlab? Everybody on HN loves to love Gitlab because they're the underdog, and the product isn't bad, but it's not that great either.


Yes, I use it for personal projects. I also use a company-hosted version at work. The built in CI is great. I can't think of a reason, other than price for companies, why to use GitHub over gitlab. Both are great, but gitlab's built-in CI I think is easier to use and better integrated.


Yeah, you just lose 6 hours of prod data on gitlab. :)




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: