John-Mark Gurney on Nostr: I reported a similar issue years ago. Because GitHub has a unified repo for forked ...
I reported a similar issue years ago.
Because GitHub has a unified repo for forked repos, you could fork a repo, commit code. Then you could submit an update to a code based that uses the form as a submodule and make it appear as if your code was part of the official repo.
GitHub's response was a minor UI improvement.
Not surprised this happened.
>
https://mastodon.social/users/asmodai/statuses/112845413158764842Published at
2024-07-26 03:28:24Event JSON
{
"id": "0612350c20fa2ddf9ae1cb52f865df02563d81c9c6aee42ede734a369b8f581e",
"pubkey": "e675b9ee45632dbdeddf3704bf513a17e49389bbf180ff1c32af9ded83d4ca0b",
"created_at": 1721964504,
"kind": 1,
"tags": [
[
"proxy",
"https://flyovercountry.social/users/encthenet/statuses/112850665735476288",
"activitypub"
]
],
"content": "I reported a similar issue years ago.\n\nBecause GitHub has a unified repo for forked repos, you could fork a repo, commit code. Then you could submit an update to a code based that uses the form as a submodule and make it appear as if your code was part of the official repo.\n\nGitHub's response was a minor UI improvement.\n\nNot surprised this happened.\n\n\u003e https://mastodon.social/users/asmodai/statuses/112845413158764842",
"sig": "aeb91aada513af27b96dca74c7a4bf916151dd1f2f18b63d2eb749c3339fadc398978011a0c7b9da4840b19cc7a57bf895a424d1b1dcb49e30fa3302ae8666d8"
}