https://firefox-source-docs.mozilla.org/testing/geckodriver/Patches.html mentions

> You can submit patches by using Phabricator.

but what repository? https://phabricator.services.mozilla.com/diffusion/query/all/ does not mention Geckodriver.
Jun 7, 10:28am

The Geckodriver source code is part of the broader Mozilla codebase and is located within the mozilla-central repository, specifically under the testing/geckodriver directory. While the GitHub repository (mozilla/geckodriver) is used for issue tracking and releases, patches should be submitted to the mozilla-central repository via Phabricator. This is confirmed by both the official Geckodriver documentation and the README in the mozilla-central repository.

So, to submit patches for Geckodriver, you should use the mozilla-central repository on Phabricator.

Jun 7, 10:29am
`mozilla-central` is denoted as inactive on https://phabricator.services.mozilla.com/diffusion/query/all/.
Jun 7, 10:32am

You are correct that the mozilla-central repository is not explicitly listed as active on the Phabricator repositories page. However, the Geckodriver source code is indeed part of the mozilla-central repository, and patches for Geckodriver are submitted through Phabricator as Differential Revisions (not via a separate repository listing).

How to Submit Patches for Geckodriver:

  1. Repository: The actual code lives in mozilla-central (Mercurial), under testing/geckodriver.
  2. Phabricator Workflow:
    • You create a Differential Revision (a patch) on Phabricator.
    • The patch is reviewed and landed in mozilla-central via the standard Mozilla contribution process.
    • The Geckodriver README even references Phabricator revisions (e.g., D241206) .

Why the Confusion?

  • Phabricator’s "Diffusion" (repository browser) may not list mozilla-central as a standalone repository because it is managed as part of Mozilla’s core infrastructure, not as a separate project.
  • The mozilla/geckodriver GitHub repo is only for releases and issue tracking, not for code contributions.

Next Steps:

  • To submit a patch, follow Mozilla’s contribution guidelines for mozilla-central.
  • Use hg (Mercurial) to clone mozilla-central, make your changes in testing/geckodriver, and submit via arc diff (Phabricator’s CLI tool).

Would you like help with the specific steps to submit a patch?

Jun 7, 10:32am

This is a shared conversation and may include unverified content that doesn't reflect Mistral AI's views. Login to resume chatting.

Vibe can make mistakes. Check answers. Learn more