3 ms·
They allow PRs against forks too, which is a useful feature for working on something until you're ready to submit it. But the answer is because GitHub doesn't
by cipherboy 7y ago
They allow PRs against forks too, which is a useful feature for working on something until you're ready to submit it.
But the answer is because GitHub doesn't distinguish what is and isn't a mirror (last I checked there was no mirror functionality like GitLab or Gitea). Plus, I don't think they let you disable PRs.
- coldpie 7y ago> But the answer is because GitHub doesn't distinguish what is and isn't a mirror They do. See the "mirrored from" text near the top of the page. These unmaintained mirrors, which GitHub created and no one owns, just collected PRs from well-intentioned users, and it's up to random other people or the maintainers of the project to go tell them how to submit properly. I've emailed GitHub support about this, as it hits the Wine project, too[1], but they refuse to do anything. It feels like a dark pattern, to try to make GitHub the one-and-only source for open source projects. One of several reasons I dislike GitHub and wish it wasn't so well embraced by the open source community. [1] https://github.com/wine-mirror/wine/pulls https://github.com/wine-mirror/wine/pulls
- cipherboy 7y agoAh TIL, it must be a new feature. Most of the mirrors I'm used to aren't truly mirrors but are "mirrors" that are synced manually/via bots and lack the little link. These are likely just regular repos. [0]: https://github.com/nss-dev/nss https://github.com/nss-dev/nss [1]: https://github.com/videolan/vlc https://github.com/videolan/vlc
- deleted 7y ago[deleted]