Tabgate

Background

Tabgate (also referred to as The Indentation Incident, The Great Reformat, and by HR as Case #2021-0315) was a workplace controversy that erupted on March 15, 2021, when Burbridge submitted a single pull request converting an entire production codebase from spaces to tabs.^[1]

The codebase in question had used 2-space indentation since its founding in 2014, a decision made by the original team lead during what has been described as "a period of poor judgment and insufficient caffeine."^[2] Burbridge had reportedly tolerated this arrangement for approximately 847 days before reaching what colleagues later described as "a calm and measured breaking point."

The Pull Request

At 6:14 AM on March 15, 2021, pull request #8,847 appeared in the team's repository. Its title was simply: "Fixed." The description field contained a single period.

The PR contained changes to 4,200 files, touching every source file in the project. Each file had been converted from 2-space indentation to tab indentation with surgical precision. No other changes were made. No logic was altered. No bugs were introduced. The CI pipeline passed on the first attempt.^[3]

"I opened the PR expecting maybe a config change. Then I saw '+4,200 files changed' and I just sat there for a while." — Anonymous reviewer, deposition transcript

The PR was self-approved and merged 22 minutes after submission. When questioned about the self-approval, Burbridge reportedly stated: "I reviewed it. It was correct. I approved it. That's how reviews work."^[4]

Fallout

The immediate aftermath of the merge was described by multiple witnesses as "quiet, then not quiet." The following events occurred within 72 hours:

• Three engineers resigned — two citing "irreconcilable differences with the indentation," one citing "I was already looking, this just accelerated things."
• One engineer was promoted — for being the only person who had been using tabs secretly in their local environment for two years.
• The .editorconfig file was updated — with a comment that read: // Do not change this. You know who you are.
• A company-wide style guide was published — it was one page long and said "Tabs."
• The Slack channel #spaces-advocacy was archived — its final message was "well."

Aftermath

The Council of Builds convened an emergency session to review the incident. After 45 minutes of deliberation, the Council ruled the PR "technically correct, which is the best kind of correct" and issued a formal commendation.^[5]

A post-mortem was conducted per company policy. The document, titled "Tabgate: What Happened and Why It Was Fine," concluded with three action items:

1. Update the style guide (completed; see above)
2. Conduct a team retrospective on "resilience in the face of correctness"
3. Buy Burbridge a coffee (status: pending, 5 years and counting)

Cultural Impact

Tabgate has become a touchstone in software development culture. The phrase "Fixed." is now widely used as a commit message when making changes that are objectively correct but socially disruptive.^[6]

A commemorative Slack emoji (:tabgate:) was created depicting a tab character wearing a crown. It remains the third most-used custom emoji in the company workspace, behind :ship-it: and :this-is-fine:.

March 15 is informally observed as "Tab Day" by a small but fervent group of developers who mark the occasion by converting one file from spaces to tabs and committing it with the message "Fixed."

References