Ask HN:GitHub 越来越不稳定了吗?

2作者: pavish6 个月前
过去几周,我注意到 GitHub 出现了一些问题,其中大部分几个月前还能完美运行。<p>除了宕机之外,还有几个令人烦恼的、最近才出现的体验:<p>- 我们的发布流程包括在 QA 之前创建草稿版本,并在准备就绪时发布。我们今天发布了一个新版本,来自美国的团队成员能够看到它已发布,而来自其他国家的成员仍然看到该版本被标记为草稿,且未公开可见。我们在发布公告后两个小时才注意到这个问题。我们不得不取消发布并重新发布才修复了它。<p>- 最近,一位同事在 GitHub 上查看差异时注意到了一些不相关的更改,这导致我们回滚了合并,但后来才注意到提交本身没有问题,问题出在 GitHub 的 UI 上。<p>宕机和重大问题是可以接受的,它们动静大,会被直接处理。而这类问题却不易被察觉,它们会悄无声息地降低信任感。<p>我现在不再信任 GitHub 的界面和操作了。我们不得不手动重新测试我们的发布资产,以确保 GH 没有搞砸。<p>这是否又是过度信任 AI 代码而没有进行适当审查和测试的结果?在内部讨论时,我的一个同事提到“最近整个互联网都感觉很脆弱”。<p>我很想知道是否还有其他人遇到过 GitHub 上的这种奇怪问题。
查看原文
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.