Hi all, This is now done. EWS only supports the GitHub pull request workflow now. The Bugzilla patch workflow (including the commit-queue) is no longer supported.
Status bubbles on existing Bugzilla patches still load their old results, and Bugzilla remains how we track issues. If you were still using the patch workflow, see https://github.com/WebKit/WebKit/wiki/Contributing to get set up with PRs. If you notice any issue, please let me know. Thanks Aakash > On Aug 3, 2026, at 4:46 PM, Aakash Jain <[email protected]> wrote: > > Hi all, > > We plan to remove support for the Bugzilla patch workflow from EWS > (ews-build.webkit.org), keeping only the GitHub pull request workflow. > > EWS has supported both workflows since GitHub PR support was added in early > 2022. Since then, almost all contributor traffic has moved to PRs. webkitbot, > the last piece of infrastructure on the patch workflow, was migrated last > month. Keeping both paths alive significantly increases the amount of code we > have to maintain and test in EWS, for very little benefit. > > What would go away: > - Submitting patches to EWS via r? on a Bugzilla attachment, and the > submit-to-EWS page. > - The commit-queue (cq+/cq-). > > Bugzilla itself is not going anywhere: bugs remain how we track issues, and > PRs will keep linking to and commenting on them as they do today. > > If you are still on the patch workflow, see > https://github.com/WebKit/WebKit/wiki/Contributing to get set up with PRs. > > Assuming no objections, we would start removing this in 2 weeks from now. > Please let me know if you have concerns, or if you have tooling or a workflow > that depends on the patch based workflow. > > Thanks > Aakash _______________________________________________ webkit-dev mailing list -- [email protected] To unsubscribe send an email to [email protected]
