[chacha102]

Fortunately, Github is built on a distributed system that doesn't require us to stop coding just because we can't access a central server.

Distributed systems for the win!

[leeoniya]

except that it also serves as a communication platform, like issues, PRs, code review, CI.

the fact that git is distributed is but a small part of the whole.

[slowmovintarget]

Which is why it gets targeted by "state actors". I'm not saying that's what this is, but it's happened before.

[YetAnotherNick]

What is distributed here? If github is down no one can see what you changed, not even the build servers. Git is distributed in the sense that every client has complete history, but not in the sense that my laptop can act as replacement of github(like torrent).

[chrisseaton]

Git supports lots of protocols for sharing your changes - even email!

[YetAnotherNick]

Diffs can be shared over mail, right. Can I do a `git pull` via mail?

[ddevault]

Yes:

https://git-send-email.io

You can also do a "request pull" over email, which if it sounds confusing it's because GitHub wanted it to:

https://www.git-scm.com/docs/git-request-pull

[chrisseaton]

You can't over mail. But each of you could run your own Git server if you wanted to be able to pull.

[IshKebab]

Git is distributed in the sense that you have a copy of the source code and can make commits. Compare this to what would happen if an SVN server went down.

[YetAnotherNick]

Even in SVN there is a copy of the current code everywhere. Just that it does not support having multiple repos and all which I don't think many people uses in git. Most orgs only have one remote repo setup(I would love to be wrong in this)

[marceloabsousa]

I wish I could agree with you - still, these outages just reveal that GitHub is much more important to software development than pushing changes into a git repository.