News for hackers. Stuff that matters.

A comment on Inviting another GitHub user to be your successor. Parent comment

Re:Inviting another GitHub user to be your successor by indigochill on Thursday January 06, 2022 @07:54AM (#29822934)
> at worst, it can break production systems.

I assume you don't mean these production systems are depending on reliable access to code in a third-party Github repo because that's fairly easily remedied by at least forking the repo once that repo becomes a dependency (not to mention potentially very dangerous in case of malicious changes), but I'm curious what the scenario you're referring to here is.

[ Parent | on HN ]
Re:Inviting another GitHub user to be your successor by dagw on Thursday January 06, 2022 @10:49AM (#29825045)
I assume you don't mean these production systems are depending on reliable access to code in a third-party Github repo

When are people going to stop feigning surprise at this? Being completely unable to deploy a new server just because pypi/npm/github etc. is down has been best practice and standard operating procedure for years now.

Keeping a complete audited mirror of everything needed to deploy your product and only pulling code for production from machines you have complete control over is so 2005.

[ Parent | on HN ]