It is now the time to start widespread testing of pure git checkouts for WebKit. Commit queue has been reimplemented for GitHub, so you don't need a Subversion or git-svn checkout for changes to trunk/main that aren’t modifying SVN properties. Over the past few months, we’ve been working on transitioning the WebKit project away from Subversion and to `git` hosted by GitHub. While we still have a few weeks of work left, we wanted to announce that the WebKit project now supports GitHub pull-requests for developing, reviewing and landing changes. We’d like to encourage folks to try out these new workflows to identify bugs and provide feedback. To get started, migrate your local WebKit checkouts to the GitHub version (documentation is available at https://github.com/WebKit/WebKit/wiki/Migration <https://github.com/WebKit/WebKit/wiki/Migration>), review our GitHub contribution documentation at https://github.com/WebKit/WebKit/wiki/Contributing#contributing-code <https://github.com/WebKit/WebKit/wiki/Contributing#contributing-code>, and start creating some pull requests! We will be collecting bugs and feedback under our umbrella bug, https://bugs.webkit.org/show_bug.cgi?id=239082 <https://bugs.webkit.org/show_bug.cgi?id=239082>. It is worth noting that while we are currently displaying EWS results via GitHub’s native checks UI, we have a plan underway to add a dynamic comment belonging to EWS that will contain information similar to the bubbles on bugs.webkit.org <http://bugs.webkit.org/>. Lastly, we have no plans yet to deprecate patch workflows. As mentioned in the migration documentation, `webkit-patch` will continue to work inside GitHub checkouts, so it is possible to use both the pull-request workflow and patch workflow from the same checkout. Jonathan Bedard WebKit Continuous Integration