GitHub 全球宕机！开发者怒骂后“大逃离”

Core Viewpoint - GitHub experienced a significant outage, leading to widespread developer frustration and speculation about the potential role of Copilot in the incident [1][3][4]. Group 1: Incident Overview - A large number of developers reported that GitHub was down, causing disruptions in development processes globally [1][4]. - GitHub acknowledged the outage, stating that multiple services were affected, particularly issue reporting, pull requests, and API functionality, and the issue was resolved after approximately two hours [5]. - Users expressed their concerns about the reliance on GitHub, questioning why so many projects are solely hosted on this platform without alternative options [7]. Group 2: Migration and Developer Response - Gentoo Linux announced plans to migrate its repositories away from GitHub, citing the forced use of Copilot as a primary reason for the decision [8][9]. - The Gentoo community criticized GitHub's attempts to compel repository contributors to enable Copilot, arguing that it disrupts normal development processes and violates open-source licensing principles [8][9]. - Personal developers are also expressing dissatisfaction with GitHub, with many considering alternatives due to the mandatory use of Copilot and concerns over its handling of open-source code [11][12]. Group 3: Copilot Controversy - Developers have raised alarms about Copilot's potential reuse of open-source code without proper attribution, leading to discussions about whether Microsoft should disable these features [12][14]. - There is a growing sentiment among developers that Microsoft's promotion of Copilot is top-down and disregards user retention, prompting many to seek self-hosted solutions or alternative platforms [15].