Why WebKit Is Moving from SVN to GitHub—and What It Means for Developers

Apple’s WebKit, the rendering engine behind the Safari browser on macOS, is preparing to migrate its source code repository from Apache Subversion (SVN) to Git, using GitHub as the primary hosting platform.

The project currently uses Subversion, but the next step is to convert to Git for source‑code version tracking and to host the repository on GitHub.

Jonathan Bedard, a WebKit engineer, explained that the move will take advantage of Git’s distributed nature and its large developer community, making it easier for multiple organizations to collaborate and submit changes.

Many new contributors to WebKit already prefer the git‑svn tool, so the transition fits existing workflows and gives developers more options.

One practical change is that Git’s hash identifiers are not naturally ordered; WebKit will adopt a “commit identifier” system that tracks the number of ancestors for each commit on the main branch, with branch identifiers combined as needed.

WebKit enforces a “zero‑tolerance performance regression” policy: if a change causes a performance benchmark regression, the patch cannot be merged.

All commits are linked through commits.webkit.org , embedding the identifier in the commit message.

Developers have questioned why the migration is happening now, noting that not everyone sees moving to Git as a good idea.

A Hacker News user commented that GitHub has experienced over 50 outages this year and restricts users from sanctioned countries, questioning the benefit of moving the project to GitHub.

Some developers describe the transition as a nightmare and difficult, even if the final product launches smoothly.

Another user argued that the migration is necessary because GitHub offers a popular UI and integrated development tools, and its widespread adoption means contributors no longer need separate accounts to contribute.

Editor: Universal Da Xiong