Live data from Hacker News

GitHub Outage Currently Ongoing – Issues, PRs, Notifications

githubstatus.com

101–106 of 106 posts

Re: GitHub Outage Currently Ongoing – Issues, PRs, Notifications

#101
post #5

Earlier quoted context omitted.

There are quite a decent list of competitors, all of which have similar or sometimes better offerings. There are also plenty of fully free and open source solutions, should you want to do things yourself. The Github monopoly is driven by its users.

I tried gitlab but I hated the web interface. It was lacking in so many departments. Any other alternatives to github to try?

- sr.ht (OSS, managed, self-hosting)

- Gitlab (sorta OSS, managed, self-hosting)

- Gitea (OSS, self-hosting)

- Gogs (OSS, self-hosting)

- Bitbucket (managed)

- Azure Repos (managed)

- Google Cloud Repositories (managed)

To be honest, Gitlab has come a long way. And things like search that people point out doesn't work well on Github either, where code search is super broken and often skips results or find nothing where a git grep would drown you in results.

Re: GitHub Outage Currently Ongoing – Issues, PRs, Notifications

#102
post #44

Earlier quoted context omitted.

On gitlab,repository and code searching function should be improved loll

Same could be said for github. I regularly literally copy and paste a variable name from a file on Github itself - paste it into the search, and it finds 0 results. HOW COULD YOU FIND NOTHING?! Not even the file I copied it from? A simple grep search would've had no issue and would've been faster!

Yeah, I always end up having to clone the repo to grep.

Re: GitHub Outage Currently Ongoing – Issues, PRs, Notifications

#103
post #77

Alright, cue the usual: Monoculture bad Microsoft bad Git is distributed but all the things around it that we really need aren't You can set up git to push to multiple remotes automatically Nobody is actually using git in distributed mode Did I forget anything?

> Git is distributed but all the things around it that we really need aren't Can anyone recommend an issue tracker that is distributed with the repo?

There were a whole bunch of these being actively developed around 2009-2012, but all of them slowly died out because each one had at least one of several issues that made them difficult or annoying to use, usually either requiring forgettable steps to actually distribute, or polluting the commits/branches with their own tracking.

My personal solution is similar to sibling comments, but more structured - using vimwiki in a subdirectory inside the repo, and committing updates alongside the relevant code changes.

Re: GitHub Outage Currently Ongoing – Issues, PRs, Notifications

#104
post #63

Earlier quoted context omitted.

I'm sorry you had a bad experience with this. The importer can still get better but we're importing about 500 projects per hour at peak https://www.dropbox.com/s/hr3ndcmu21aehmk/Screenshot%202019-...

Some imports work. The ones that failed are those with release notes (which were also the more important ones). And they fail silently (succeeded but no releases imported), which is annoying. I could dig up the issue numbers. I'm generally very pleased with GitLab. I'm delighted that it's open source.

Glad to hear; I'd really like to see us improve some of our import capabilities at GitLab. We've created a separate team specific to importers and have started moving much more quickly here. Thanks for your patience.

Please let me know if this issue addresses the problem you encountered, would love to make sure we're prioritizing it. https://gitlab.com/gitlab-org/gitlab-ce/issues/20780

Re: GitHub Outage Currently Ongoing – Issues, PRs, Notifications

#105

Earlier quoted context omitted.

Irony of ironies. Gitlab's import-from-GitHub functionality has been broken ever since we tried to migrate away. (They're going ot fix it soon.)

I did this for the first time 2 days ago on two medium-size GH repos and it while was crazy slow, it eventually completed after about 8 hours or so. The actual bits seemed to finish in a relatively quick amount of time, but the project landing page continually showed "import in progress" for all those 8 hours.

Git is simple to import, but all other related data may be subject to API rate limits.

I've opened an issue with some improvements suggestions, like surfacing when we are rate limited and allowing gradual access to the data while the import is going on: https://gitlab.com/gitlab-org/gitlab-ce/issues/66525

Re: GitHub Outage Currently Ongoing – Issues, PRs, Notifications

#106

Earlier quoted context omitted.

Some imports work. The ones that failed are those with release notes (which were also the more important ones). And they fail silently (succeeded but no releases imported), which is annoying. I could dig up the issue numbers. I'm generally very pleased with GitLab. I'm delighted that it's open source.

Glad to hear; I'd really like to see us improve some of our import capabilities at GitLab. We've created a separate team specific to importers and have started moving much more quickly here. Thanks for your patience. Please let me know if this issue addresses the problem you encountered, would love to make sure we're prioritizing it. https://gitlab.com/gitlab-org/gitlab-ce/issues/20780

I think these issues were implicated:

https://gitlab.com/gitlab-org/gitlab-ce/issues/65194 https://gitlab.com/gitlab-org/gitlab-ce/issues/52956

No idea when these are going to be deployed. 12.2, 12.3, 12.5... But I'll keep checking in and trying the import every few weeks.

Post reply on HN