4 ms·
> You still cannot disable pull requests on a GitHub repository. A package repository might deem your software “critical”, adding requirements to publishing upd
by kazinator 4y ago
> You still cannot disable pull requests on a GitHub repository. A package repository might deem your software “critical”, adding requirements to publishing updates that you might not want to or be able to comply with. Google even wanted to disallow anonymous individuals from maintaining critical software and wanted to police the identities of others.
That's just whining from people who host their stuff on other people's servers and sites.
If other people package your software into a bigger system and then later improve their standards so that the bar is above your stuff now (e.g. you break it left and right with careless, untested changes, or whatever, whereas downstream is doing actual QA) that's downstream's prerogative. You don't have to do anything; they can fork your stuff and develop it themselves, or stick with the old version from you that worked, ignoring the newer releases.
- LtWorf 4y agoThe problem is that they don't fork it. Instead they harass you.
- kazinator 4y agoPeople should give that a good try; maintaining forks sucks. In the past I've forked at the sign of any resistance. I have a fork of GNU Awk called Enhanced GNU Awk (egawk). https://www.kylheku.com/cgit/egawk/about/ https://www.kylheku.com/cgit/egawk/about/ It has a let construct for lexical variables. Chances are it's not packaged for your favorite OS, so you'd have to build it yourself. The next thing on the plate for that project is to support the GNU C preprocessor line annotations so that if Egawk is handed preprocessed code, it will report errors against the original file and line number.