【记录】Github|Github账号意外被封以及不需要手机号解封的全过程(被封原因:一台设备上登录过多个账号)

【记录】Github|Github账号意外被封以及不需要手机号解封的全过程(被封原因:一台设备上登录过多个账号)

文章目录

前言

一开始被封我以为是我发表了不当言论,因为我刚发一条discussion就被封了,但是后面发现这不是根本原因。应该是之前有人看我【记录】Copilot|Github Copilot重新学生认证通过方法(2025年7月,包括2FA和认证材料、Why are you not on campus)问我怎么教育认证不通过的时候,我尝试帮他认证了一下(但最后还是在他自己的电脑上提交的认证材料)。

总之被封号很可能与发了discussion(导火索)、教育优惠(底层原因)和小号(封号的明面理由)有关,如果你是因为其他问题,解锁请参考一下其他人的经验。

  1. 仓库违反 DMCA:分享下我 GitHub 被封的经历 - www.leavesongs.com
  2. 不打算解封只打算备份账号:分享一次我github被封的经历以及迁移指南 - linwu - 知乎
  3. 系统风控监测到密码泄露:记录 Github 账号意外被封后恢复 - v2ex

关于 discussion 是封号导火索的例证:github 被封的经历 - 分享一下要注意避免的行为

在这里插入图片描述

解封全过程

全过程可以直接参考Github自己发的解封教程(中文版):
https://docs.github.com/zh/site-policy/acceptable-use-policies/GitHub 申诉和恢复

网上都说要手机号,实则不然。
只要邮箱就可以。
甚至我用的是qq邮箱都行。

根据这个教程你们可以看到它要求6个月内就发起申诉,不然它们有权永远拒绝你的申诉。如果你看到这篇博客的时候已经晚了,可以去这个链接备份一下你自己的star列表,[username]填自己的账号名:https://api.github.com/users/[username]/starred。

提交工单

如果你想跳过引导,你可以直接点击这个链接提交工单:https://support.github.com/contact-next/product-selection/account-restrictions

一步步跟着引导到提交工单的过程如下:

在这里插入图片描述

在这里提交:https://support.github.com/contact/cannot_sign_in

填写电子邮箱,然后选择账号被锁定,再过一下它弹出的验证码:

在这里插入图片描述

之后会发一封邮件到邮箱里:

在这里插入图片描述
在这里插入图片描述

然后你可能会看到两个不同的页面:

页面一 账号微死

我的账号已经申诉成功了所以我没有办法来到这个微死的页面,我这里引用了这个博主的图:https://blog.ZEEKLOG.net/qq_75136161/article/details/137755898

在这里插入图片描述
工单内容

我是一气之下就直接提交了,也没参考别人的教程……甚至我都忘记了要表达严谨清楚,说我账号被disable了……

在这里插入图片描述


我的填写内容(可以看出来已经急得开始胡言乱语把向微软提交过pr都加进来了……都是些文档类型的pr):

# Does your claim involve content on GitHub or npm.js? GitHub # What is the username and repository or package name that was impacted? shandianchengzi # Why are you requesting reinstatement? If you are requesting support for your account not related to moderation limits made on your account by GitHub please raise a support ticket instead. My account was disabled and I can’t login # Have you previously contacted GitHub about this claim? No # Would you like to provide any additional information or context that would be helpful for our review of your reinstatement request? I published a usual discussion in an organization,and then my account is blocked! "Access to your account has been suspended due to a violation of our Terms of Service." I don't know why. I have over 100 repos and 59 followers in github, and commit for many repos including Microsoft's.# I have reviewed and understand the GitHub Acceptable Use Policies and Community Guidelines.

页面二 账号微活

我在账号死了的时候看到这个页面一是因为我在尝试拿小号交工单……请务必不要学我的行为,因为github不支持小号;二是因为提交完页面一的内容之后好像会自动跳转到这里允许补充说明更多情况。

点击联系Github支持:

在这里插入图片描述


选择Account Restriction:

在这里插入图片描述


最终会来到这个页面:
https://support.github.com/contact-next/product-selection/account-restrictions

在这里插入图片描述
工单内容

我记得我是直接粘贴的一个博主的工单,但是我找了很久也没找到具体是谁。

毫无感情正经申诉版本(推荐)

Subject:Account suspend: [Your GitHub Username]
Issue(可以狡辩自己没用小号,是拜托朋友帮忙申诉,我是狡辩了的,不过我现在已经把小号删了也忘了自己是怎么说的了。正常的申诉可以按下面这个思路):

这个模板来自:GitHub 封号申诉工单模板 - 博客园
Dear GitHub Support Team I hope this message finds you well. I am writing to request the reinstatement of my GitHub account, which was recently suspended. My account username is [Your GitHub Username], and the email associated with the account is [Your Email Address]. I kindly ask for your assistance in reactivating my GitHub account. Thank you for your attention to this matter. Best regards 

后面如实填写。

我小号发了这个工单之后,收到回复说让我别用这个账号登录提交工单,去那边正经的工单提交;我说正经工单不理我能不能帮我催一下,我忘记他怎么回复的了,也不知道起没起作用,反正最终我的正式工单收到了回复。

带情绪的申诉版本

我申诉的时候是猜测编辑的discussion有问题,但是我没有证据,我只能在申诉的时候道歉,但是我又不觉得自己有问题,最后就是礼貌又客气地发了一封抱怨的issue(不要学我,最好是直接说自己要申诉、不知道为什么被封就好了):
Subject:Account suspend: [Your GitHub Username]

Dear GitHub Support Team, I’m writing to follow up on my previous appeal regarding the suspension of my account (shandianchengzi). I wanted to provide additional context to assist with your review: My account has been active for nearly six years with 59 followers, and I’ve consistently contributed to open-source projects in good faith. The suspension may have been triggered by either: 1. Unintentional Sensitive Content: While developing a word-cloud tool for current affairs, I might have overlooked politically sensitive material requiring desensitization. 2. Automated Flagging: The volume/length of my recent edits could have been misclassified as AI-generated spam. I deeply regret any oversight and will ensure strict adherence to GitHub’s policies moving forward. This account is critical to my work and studies, and I’d be grateful for the opportunity to correct any mistakes. Thank you for your time and reconsideration. Please let me know if further details are needed. Best regards, shandianchengzi 

后面如实填写。

邮件battle过程

我是周末提交的工单,所以确实一时半会儿不会收到回复。
等了几天之后收到了邮件回复,之后的信息都在邮件中回就行。

回的时候可以用gemini辅助一下,它比较理智冷静,对国外社区的规范也熟悉一些——换成deepseek能吵起来。

Round 1:搞清楚怎么被封的

GitHub Support

Hi there,

Thank you for contacting GitHub Support.

Sometimes our abuse detecting systems highlight accounts that needs to be manually reviewed.

Upon review, it seems your account has restrictions imposed due to violating our terms, it appears you may have created more than one free account which is in violation of the GitHub Terms of Service.

We will be happy to further review this account if you could validate to us in writing that you would keep to our terms and merge or delete the additional accounts you no longer want to use.

Best regards,
Wick

分析

它说是因为违反服务协议被封的,我点进去看了服务协议,说Github不支持小号。但是我的小号是好多年之前注册的,早不封晚不封,怎么现在突然封了,肯定根本原因不是这个。但是我还是要先删除我的小号然后道歉。

Round 2: 删除已知小号然后道歉

这里把小号的名字脱敏了,因为小号名称比较有针对性。

Me

Hi Wick,

Thank you for the notification and for clarifying the restriction on my account.

I sincerely apologize for inadvertently violating the GitHub Terms of Service by having more than one free account.

I have already taken immediate action and permanently deleted what I believe to be the second account you referred to, which was associated with the URL https://github.com/xxx and the email [email protected]. This account was created for temporary machine use and I apologize for the oversight in failing to delete it sooner.

I formally confirm in writing that I will strictly adhere to GitHub’s Terms of Service moving forward, including the policy regarding a single free account per user.

I look forward to the resolution of this matter and having the restrictions removed.

Thank you for your understanding and assistance.

Best regards,

shandianchengzi

分析

我其实看完服务协议很不服气,因为我的那个小号就是个机器人临时小号,不违反他们的服务协议,所以我虽然删了但是一点也不爽。但是我在Gemini的劝诫下还是发了一封心平气和的邮件,只是夹带说了一句只是temporary machine use。

Round 3: 处理所有小号

Github Support

Github那边列出了我所有的小号(甚至还有一些号不是我的):
Hi there,

Thanks for your response.

Please see the list of associated accounts.

xxx1 shandianchengzi xxx2 shandianchengzi xxx3 

We’d ask you merge your accounts or delete one of them using these steps

Merging multiple personal accounts
Deleting your personal account

Please let me know if you need anything else.

Best regards,
Wick

分析

可以看出来他们判定小号就是在同一台设备或者同一个IP上一起登录过。有些账号不是我的肯定不能删,所以还是得进行新一轮的argue,不过不能跟他说我是为了教育优惠帮别人临时登录,不然万一他觉得我有问题把我教育优惠停了我上哪说理去。

但是好在他发完这个消息,我就能登录了。

Me

除了账号问题我还发现我的follower被清空了,我也一并跟他说了。

Hi Wick,

Thank you for providing the list of associated accounts. I have taken immediate action to ensure I comply with GitHub’s Terms of Service, and I would like to clarify the status of each account listed:

  1. Accounts Managed/Deleted by Me
    xxx1: This was an empty, temporary account. I have permanently deleted it immediately using the provided steps.
    shandianchengzi: This is my sole, active account that I intend to keep using. I formally confirm that I will only maintain this single free account moving forward.
  2. Accounts Not Owned or Controlled by Me
    xxx2: This account does not belong to me. I briefly logged into this account only once, at the owner’s request, to assist with a minor billing name configuration issue. I have no control or access to this account, and the owner regularly accesses it from a different geographical area.
    xxx3: This account does not belong to me. It was created by me for my friend, using her email and password, for a specific, temporary programming project. I have since lost access to this account and cannot merge or delete it as I am not the owner and do not know the current password.
  3. Follower Count Issue
    Now that I have addressed all the accounts I can control, I have noticed an issue with my main account, shandianchengzi. When logging in, I found that my Followers and Following counts have both been reset to zero (0).
    Could you please confirm if this is a side effect of the review process? I would like to know if these counts can and will be recovered once my account compliance status is fully restored.

Thank you for your assistance in finalizing the account review and addressing the follower count issue. I look forward to your positive confirmation.

Best regards,

shandianchengzi

Round 4: 后续关于follower和fork权限等问题

总之就是他承诺会恢复,但是等了很久也没恢复,我问他怎么回事,但是问了也没用,他说我的工单被转移给别人了。过了大概半个月终于正常了。

Github Support

Hi there,

Thanks for your response.

We’ve cleared the restrictions from your account, so you have full access to GitHub again.

Regarding you question on the follower count issues, It’s normal to see Followers/Following temporarily show as 0 after an account review. Once your account is fully reinstated, those counts are recalculated and typically return within a few hours (sometimes up to 24 hours). If you still see 0 after about a day, let me know and I’ll run a refresh on our side to restore the correct counts.

Please let me know if you need anything else.

Best regards,
Wick

Me

Hi Wick,

Thank you very much for confirming that the restrictions have been cleared from my account. I appreciate your assistance with the review process.

I am writing to follow up on a few lingering issues, as I have now waited approximately six days, exceeding the 24-hour timeframe you mentioned for the account state to fully refresh:

Follower Count Issue: My profile’s Followers count still displays as 0. However, when I click on the count, I can see the actual list of my followers, indicating the data is present but the count is not displaying correctly.

Functionality Limitations: I have noticed two other persistent functional limitations, which suggest the account state is not yet fully reinstated:

I cannot fork any repository.

I cannot accept invitations to join others’ private repositories.

Given these continued issues, could you please run the refresh operation on your end as you previously suggested to fully restore my account’s functionality?

Thank you for your time and continued support in fully reinstating my account.

Best regards,

shandianchengzi

Github Support

Hi again,

Thank you for writing back.

I am going to route your ticket to the team that is better suited to assist you with this. Someone from that team will reach out to you with next steps or further questions.

I hope this helps to clear things up. Feel free to reach out again at anytime should you have any additional questions.

Best regards,
Wick

尾声

总之不要创建小号也别登别人的账号吧,然后就是少发discussion免得触发github的风控检查。

本账号所有文章均为原创,欢迎转载,请注明文章出处:https://shandianchengzi.blog.ZEEKLOG.net/article/details/155768104。百度和各类采集站皆不可信,搜索请谨慎鉴别。技术类文章一般都有时效性,本人习惯不定期对自己的博文进行修正和更新,因此请访问出处以查看本文的最新版本。

Read more

Alf.io:为什么这是活动组织者的终极开源票务解决方案?

Alf.io:为什么这是活动组织者的终极开源票务解决方案? 【免费下载链接】alf.ioalf.io - The open source ticket reservation system for conferences, trade shows, workshops, meetups 项目地址: https://gitcode.com/gh_mirrors/al/alf.io 在当今数字化时代,活动组织者面临着前所未有的挑战:如何高效管理票务销售、确保数据安全、同时提供出色的用户体验?Alf.io作为一款完全开源的活动票务管理系统,正是为解决这些痛点而生。这个基于Java 17和Spring Boot构建的专业平台,为各类活动提供从票务创建到签到管理的完整解决方案。 🎯 核心优势:专业级功能满足多样化需求 Alf.io不仅仅是简单的票务销售工具,它提供了一套完整的活动管理生态系统: 完整的票务生命周期管理 * 活动创建与基本信息配置 * 多票种分类与价格策略设置 * 实时容量监控与销售统计

By Ne0inhk

GitHub界面中文化终极方案:5分钟让GitHub说中文的完整教程

GitHub界面中文化终极方案:5分钟让GitHub说中文的完整教程 【免费下载链接】github-chineseGitHub 汉化插件,GitHub 中文化界面。 (GitHub Translation To Chinese) 项目地址: https://gitcode.com/gh_mirrors/gi/github-chinese 还在为GitHub复杂的英文界面而头疼吗?GitHub中文插件正是你需要的解决方案。这款强大的GitHub汉化工具能够将GitHub的英文界面瞬间转换为亲切的中文,让你在熟悉的语言环境中高效管理代码项目。 🚀 准备工作:安装脚本管理器 首先需要为浏览器安装用户脚本管理器,这是运行GitHub中文插件的基础环境: 主流浏览器安装指南: * Chrome/Edge浏览器:访问扩展商店搜索"Tampermonkey" * Firefox浏览器:在附加组件中寻找"Violentmonkey" * Safari浏览器:下载专用的用户脚本管理器应用 成功安装后,浏览器工具栏会显示相应的脚本管理器图标,这意味着你的中文翻译助手已经准备就绪!

By Ne0inhk
从 0 到 1!Qwen3.5 系列开源大模型本地部署全流程(ModelScope)

从 0 到 1!Qwen3.5 系列开源大模型本地部署全流程(ModelScope)

【本文作者:Troy】 1.Qwen Qwen3.5是阿里云通义千问团队发布的新一代开源大模型系列,是提供基础智能能力的“大脑”。主要是作为基础模型,本身具备强大的文本生成、复杂推理、多模态理解(如图像、视频)和工具调用等能力。适用于希望直接使用高性能大模型,或将其作为基座进行二次开发的个人、研究者和企业。 可访问魔搭社区:https://www.modelscope.cn/models?name=qwen3.5&page=1&tabKey=task  Qwen3.5 具备以下增强特性: * 统一的视觉-语言基础:在多模态 token 上进行早期融合训练,在推理、编码、智能体和视觉理解等基准测试中,跨代际表现与 Qwen3 持平,并优于 Qwen3-VL 模型。 * 高效混合架构:

By Ne0inhk

Fast-GitHub终极指南:彻底告别GitHub访问卡顿

Fast-GitHub终极指南:彻底告别GitHub访问卡顿 【免费下载链接】Fast-GitHub国内Github下载很慢,用上了这个插件后,下载速度嗖嗖嗖的~! 项目地址: https://gitcode.com/gh_mirrors/fa/Fast-GitHub 国内开发者在使用GitHub时经常面临下载速度缓慢、页面加载卡顿的困扰。当您急需获取开源项目代码时,git clone命令却卡在下载阶段;当团队协作需要快速访问GitHub仓库时,页面却迟迟无法加载完成。这些场景不仅影响工作效率,更让开发者倍感焦虑。 🎯 核心痛点深度剖析 GitHub访问缓慢的根本原因在于网络路由的复杂性。传统的网络连接需要经过多个中转节点,每个节点都可能成为瓶颈。特别是在高峰时段,网络拥堵会导致请求超时、下载中断等问题。 Fast-GitHub通过本地化智能加速技术,无需复杂配置即可实现访问速度的跨越式提升。插件内置多节点切换机制,能够自动选择最优的GitHub访问路径,从根本上解决网络延迟问题。 📥 一键安装完整流程 环境准备与文件获取 首先需要从官方仓库获取插件文件。打开终

By Ne0inhk