this post was submitted on 13 Nov 2025
96 points (99.0% liked)

Opensource

4358 readers
34 users here now

A community for discussion about open source software! Ask questions, share knowledge, share news, or post interesting stuff related to it!

CreditsIcon base by Lorc under CC BY 3.0 with modifications to add a gradient



founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] somewa@suppo.fi 20 points 1 week ago (8 children)
[–] Kissaki@programming.dev 7 points 1 week ago (6 children)

Looks like it's just random commenters taking random guesses because those have happened before.

What is a “repository reset”? One commenter writes:

There was a temporary similar “outage” back in July with rewritten history, apparently something inappropriate was recorded in the repo history they wanted cleaned out. The repo came back after that. I have no idea if this is the same thing, or if they just got tired of maintaining it.

Seems strange to me. You can prep locally and then force-push. I don't see why rewriting history would require taking the repository down.

[–] somewa@suppo.fi 4 points 1 week ago (3 children)

If he pushed something he shouldn't have online then taking it offline immediately makes a lot of sense.

[–] orygin@piefed.social 6 points 1 week ago* (last edited 1 week ago) (1 children)

It makes sense, but once it's pushed there is no way to know if it's been cloned or kept somewhere else. The only real mitigation is to rotate the keys or password that was leaked.
If it's something else you can't rotate, you're screwed.

[–] onlinepersona@programming.dev 5 points 1 week ago (1 children)
[–] somewa@suppo.fi 2 points 1 week ago* (last edited 1 week ago)

The point wasn't that it's not accessible but limiting the damage while you still can.

load more comments (1 replies)
load more comments (3 replies)
load more comments (4 replies)