GitHub was down
161–170 of 253 posts
Re: GitHub was down
#162I would love to see a chart of traffic to other sites when GitHub goes down. My bet is that HackerNews and Twitter both get significant spikes from all those bored developers.
Re: GitHub was down
#163I would love to see a chart of traffic to other sites when GitHub goes down. My bet is that HackerNews and Twitter both get significant spikes from all those bored developers.
> bored developers Bored? Git's a distributed version control system, so no excuses. Get back to work! But in all seriousness I kind of wish GitHub provided a way to mirror things like issues and PRs so you never have to be fully reliant on one service. Not being able to read these really does make it impossible to get work done offline.
It doesn't mirror issues and PRs but it can do a one time import of them https://docs.gitlab.com/ee/workflow/importing/import_project...
Re: GitHub was down
#164Earlier quoted context omitted.
"major inspiration for VS Code" Which is a Microsoft product, and Microsoft is the inventor of EEE. Ergo, GitHub is complicit in an EEE attempt. Q.E.D. Case closed. /s
So anyone who releases open-source code, that Microsoft might use in another open-source project is complicit in EEE? wow.
Re: GitHub was down
#165Earlier quoted context omitted.
If only you were using a decentralized VCS, you wouldn't have this single point of failure…
The problem isn't the VCS part so much as all the code review/project management features of Github. I seem to remember there was a decentralized VCS which included issue tracking besides commits, but it never was mainstream.
Re: GitHub was down
#166see:
https://github.com/clehner/git-ssb
https://github.com/noffle/git-ssb-intro
It's been working fairly well so far. We are using git-ssb to manage a few projects instead of putting them into Github.
Re: GitHub was down
#167Earlier quoted context omitted.
We have Gitlab Enterprise and it has trouble scaling.
O crap I meant to say GitHUB Enterprise. That's what has trouble. We also have Gitlab Enterprise and that's fine. Sadly for reasons internal we are mostly stuck with GitHub E.
Re: GitHub was down
#168Earlier quoted context omitted.
>Insert remark on why we use a centralized service for a distributed source control system, Because Linus didn't put features into Git that Github solves. You must break apart the different features of Github: #1) communication (issues tracking, bug reports, pull requests, README.MD landing page, etc) #2) hosting disk storage & bandwidth #3) distributed source code merges based on content hashes (SHA1) instead of usi…
#1 can be done by creating a separate submodule repo that only stores docs+issues files. It's up to the repo's users to agree on a system by which the files should be organized, but it's doable. I'd propose directories "issues/open", "issues/closed", with each issue filename being "{created:yyyy-MM-dd} - {subject}.md". Symlinks could be used to track ownership/responsibility if each repo contributor has their own dir…
Re: GitHub was down
#169If anyone is interested, I've been working with a git host that is actually distributed across a p2p network using SSB. see: https://github.com/clehner/git-ssb https://github.com/noffle/git-ssb-intro It's been working fairly well so far. We are using git-ssb to manage a few projects instead of putting them into Github.