Daniel Micay on Twitter: "@egyp7 @MisterCh0c @github Each person with a copy of the repository (whether or not it was a fork) would have to send them own DMCA counter-claim if they wanted to contest it. They don't apply these things globally or based on the fork networks. Only private repositories have a system like that." / Twitter

I don't think I've ever heard of this happening. Any GitHub experts know the circumstances under which all forks of a repo would be deleted?

@github

?

Quote Tweet

D̒͂̕ᵈăᵃn̕ᶰ Ť̾̾̓͐͒͠ᵗe͗̑́̋̂́͡ᵉn̅ᶰtᵗl̀̓͘ᶫe̓̒̂̚ᵉrʳ

@Viss

Jun 4, 2019

Replying to @jw_sec and @egyp7

I am certainly no github expert - but I know that i've seen people post like, PoCs of various hax, then i fork the repo, then they get skittish and take the repo down, and my fork goes away too. so now i download zip vs fork.

1

Replying to

and

I don't think that can happen with public repositories, including repositories that are public and then made private after being forked. Private repositories can be set up with weird restrictions though.

1

This Tweet is from a suspended account. Learn more

Replying to

and

Oh, wow, just particular files in a repo? What did the git history look like?

2

Replying to

and

Forks can't be changed by the owner of the project they were based on but you can have access to a private repository taken away, and in that case you can lose access to your fork, but I'm not sure exactly what happens to the repository (deleted vs. simply made inaccessible).

1

Replying to

It sounds like the tweet you're replying to is talking about something like a DMCA takedown notice or sensitive data removal. They treat forks as separate things, but someone submitting the request can include them: help.github.com/en/articles/gi help.github.com/en/articles/gu

1

Replying to

I've dealt with a situation where someone had a dispute with their former over the copyright / licensing of code that was released as open source and incorporated into the Android Open Source Project, and they'd repeatedly get all copies taken down. github.com/github/dmca/se

1

Replying to

Each person with a copy of the repository (whether or not it was a fork) would have to send them own DMCA counter-claim if they wanted to contest it. They don't apply these things globally or based on the fork networks. Only private repositories have a system like that.

3:03 AM · Jun 4, 2019Twitter Web Client

Replying to

Since

was talking about PoC exploits, it sounds like it was a private repository and they either removed it or revoked access which wiped out his fork. It confirms in help.github.com/en/articles/ma that forks of a private repository are deleted if your access is revoked.

1

Replying to

I thought you might get back access to your fork if they gave you back your access to the main private repository, per the official documentation it's permanently deleted... GitHub has had much stranger designs for features like how issue / commenting editing worked though.

Conversation