问HN:GitHub是否变得越来越不稳定?

2作者: pavish大约 2 个月前原帖
在过去几周,我注意到 GitHub 上出现了几个问题,其中大多数在几个月前都能正常工作。<p>除了停机问题之外,还有几个令人烦恼的、非常近期的经历:<p>- 我们的发布流程包括在质量保证(QA)之前创建草稿版本,并在准备好后发布。今天我们发布了一个新版本,美国的团队成员能够看到它已发布,而来自其他国家的成员仍然看到该版本标记为草稿,并且不对外公开。我们在发布公告两小时后才注意到这个问题。我们不得不取消发布并重新发布以解决这个问题。<p>- 最近,一位同事在审查 GitHub 上的差异时注意到了一些无关的更改,这导致我们撤回了一个合并,后来才发现该提交本身没有问题,问题出在 GitHub 的用户界面上。<p>停机和重大问题是可以接受的,它们显而易见并会直接得到解决。这类问题却常常被忽视,并且会悄悄地降低信任度。<p>我对 GitHub 的界面和操作不再信任。我们不得不手动重新测试我们的发布资产,以确保 GitHub 没有搞砸。<p>这是否又是因为过于信任 AI 代码而没有进行适当的审查和测试所导致的?在内部讨论时,我的一位同事提到“最近整个互联网感觉脆弱”。<p>我很好奇是否还有其他人也遇到过类似的奇怪问题。
查看原文
I have been noticing several issues with GitHub over the last few weeks, most of which used to work flawlessly a few months ago.<p>The outages aside, a couple of annoying, super-recent experiences:<p>- Our release process involves creating draft releases before QA, and publishing them when ready. We published a new release today and team members from the US were able to see it as published while members from different countries still saw the release marked as a draft and not visible publicly. We only noticed it two hours after making our announcements. We had to unpublish and publish it again to fix it.<p>- Recently, a colleague noticed a number of unrelated changes while reviewing a diff on GitHub, which led to us reverting a merge, only to later notice that the commit itself had no issues and it was the GitHub UI.<p>Outages and major issues are fine, they are loud and addressed directly. These kinds of issues go unnoticed, and they reduce trust silently.<p>I no longer trust the GitHub interface and actions. We had to re-test our release assets manually to make sure GH didn&#x27;t mess that up.<p>Could this be yet another result of trusting AI code too much without proper review and testing? While discussing internally, one of my colleagues mentioned that &quot;the whole internet feels fragile lately&quot;.<p>I&#x27;m curious to hear if anyone else has been facing such weird issues with GitHub.