What Happens When GitHub Silently Deletes Russian Developers’ Contributions?

Earlier we reported that GitHub blocked accounts of Russian developers due to U.S. sanctions.

Apple developer community projects Quick and Nimble suffered when their maintainer Jesse Squires discovered that many pull requests, issues, and comments from suspended accounts vanished.

Squires explained that after releasing Quick 5.0, several PRs were deleted and entire contributor histories disappeared, with messages like “All activity related to that user has vanished.”

He cited a critical bug‑fix PR #1129 that appeared in the automatically generated release notes:

@BobCatC made their first contribution in #1129

However, the user’s account and the PR now return 404 errors, though the merge commit remains.

Another maintainer, Rachel Brindle, opened a PR that also vanished because the original PR that introduced the bug had been deleted.

These “mysterious disappearances” stem from GitHub’s abrupt suspension of Russian developer accounts without considering the destructive side effects.

All affected contributors have lost their PRs, issues, comments, and discussions—essentially their entire activity—leaving only the raw Git commit history as if the users never existed.

GitHub provides no notice or explanation for these bans, unlike services such as Twitter that display placeholder profiles.

The author argues that the proper solution would be to freeze suspicious accounts, retain all contributions, and clearly mark suspended profiles, rather than deleting all associated data.

In summary, GitHub’s handling of account suspensions is harmful and destructive to open‑source projects and their communities.