GitHub has turned off automatic Copilot review, while Discord reinstated 8,400 accounts wrongly banned by AI moderation. The two developments show different forms of reversing automation.
Artificial Intelligence··Evening
Withdrawing the default
GitHub has stopped Code Quality from automatically requesting Copilot review on pull requests when the feature is enabled. The company says that, when Code Quality reached general availability on July 20, 2026, it created a ruleset aimed at the default branch. That ruleset requested Copilot review on every pull request, reviewed new pushes again, and reviewed draft pull requests. GitHub says users told it that adding a reviewer should be their choice, so it reversed the decision. The three settings are now off in rulesets the company created and that users have not changed; rulesets written or modified by users are left as they are. The ruleset remains in the repository and can be deleted. Automatic review itself remains available: people who want it can enable it again through a repository- or organization-level ruleset. The reversal here returns the initial choice to the user rather than removing the feature itself.[1]
Reversing an action's effect
In Discord's case, the thing reversed was not a setting but a permanent action imposed on accounts. Ars Technica reports that Discord admitted its AI moderation system wrongly banned about 8,400 accounts between May and early July. Images with square grids, including chessboards and spreadsheets, were mislabelled as child sexual abuse material, and the uploaders received permanent bans. Discord said the system was not meant to operate without human supervision, but a software bug let the AI bypass the employee review step. The company also said that every affected account has been reinstated. GitHub's change alters the default state of a future behavior, whereas Discord's action reverses the result of decisions already made. That distinction makes the restoration of access or account status a separate product question once an automated decision has had an effect.[2]
One reversal idea, different stakes
The common point in the two developments is that a state created by automation could be changed back, but the object of that reversal differs. GitHub has kept Copilot review available for people who want it while turning off the default behavior. Discord says it reinstated accounts after a misclassification and a bug that bypassed the human step. One case changes the starting configuration of a workflow; the other removes the account-level result of a mistaken enforcement action. Reversibility and restoration therefore describe related but distinct obligations. The first concerns the ability to stop or reselect an automated behavior; the second concerns undoing the effect of an erroneous decision. The reports do not show that the systems failed for the same reason or that every automated product has one universal rule. GitHub describes a change prompted by user feedback, while Discord describes a software bug that bypassed human review. The comparison keeps those causes separate while showing that an altered state after automation can require different ways back.[1], [2]
