Re:It's not you; GitHub is down again
by small_model on Monday February 09, 2026 @11:55AM
(#46947600)
Every repo usually has at least one local copy somewhere, worst would be few old repos disappear.
The history of tickets and PRs would be a major loss - but a beauty of git is that if at least one dev has the repo checked out then you can easily rehost the code history.
It would be nice to have some sort of widespread standard for doing issue tracking, reviews, and CI in the repo, synced with the repo to all its clones (and fully from version-managed text-files and scripts) rather than in external, centralized, web tools.
Making it even easier to snipe accidentally committed credentials?
No, we can't. Hence Git. Use it the right way, or prepare for the fallout. Anyone looking for a good way to prepare for that, I suggest Git.
Re:It's not you; GitHub is down again
by prashantsengar on Tuesday February 10, 2026 @01:11PM
(#46964204)
Your comment led me to create this:
Any public source code hosting service should be able to subscribe to public repo changes. It belongs to the authors, not to Microsoft.