1Submitting patches 2================== 3 4You can submit patches by using [Phabricator]. Walk through its documentation 5in how to set it up, and uploading patches for review. Don't worry about which 6person to select for reviewing your code. It will be done automatically. 7 8Please also make sure to follow the [commit creation guidelines]. 9 10Once you have contributed a couple of patches, we are happy to sponsor you in 11[becoming a Mozilla committer]. When you have been granted commit access 12level 1, you will have permission to use the [Firefox CI] to trigger your own 13“try runs” to test your changes. You can use the following [try preset] to run 14the most relevant tests: 15 16 mach try --preset geckodriver 17 18This preset will schedule geckodriver-related tests on various platforms. You can 19reduce the number of tasks by filtering on platforms (e.g. linux) or build type 20(e.g. opt): 21 22 mach try --preset geckodriver -xq "'linux 'opt" 23 24[Phabricator]: https://moz-conduit.readthedocs.io/en/latest/phabricator-user.html 25[commit creation guidelines]: https://mozilla-version-control-tools.readthedocs.io/en/latest/devguide/contributing.html?highlight=phabricator#submitting-patches-for-review 26[becoming a Mozilla committer]: https://www.mozilla.org/en-US/about/governance/policies/commit/ 27[Firefox CI]: https://treeherder.mozilla.org/ 28[try preset]: https://firefox-source-docs.mozilla.org/tools/try/presets.html 29