Bug 1748845 - Update source-relative links in remote docs, r=firefox-source-docs-reviewers,webdriver-reviewers,sylvestre,whimboo

These were broken since the update to MyST.

Differential Revision: https://phabricator.services.mozilla.com/D135381
This commit is contained in:
James Graham 2022-01-11 10:48:20 +00:00
parent 3d92bd280b
commit 998e7b9425
12 changed files with 36 additions and 37 deletions

View File

@ -46,6 +46,6 @@ them, place this in your [mozconfig]:
[remote/ in central]: https://searchfox.org/mozilla-central/source/remote
[mozconfig]: ../build/buildsystem/mozconfigs.html
[mozconfig]: /build/buildsystem/mozconfigs.rst
[artifact builds]: https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Artifact_builds
[Marionette]: ../testing/marionette/index.html
[Marionette]: /testing/marionette/index.rst

View File

@ -68,6 +68,6 @@ This will run the linters on the changed files before a push and
abort if there are any problems. This is convenient for avoiding
a try run failing due to a simple linting issue.
[mozlint]: /tools/lint/usage.html
[mozlint]: /code-quality/lint/index.rst
[eslint]: https://eslint.org/
[enable automatic linting]: https://firefox-source-docs.mozilla.org/tools/lint/usage.html#using-a-vcs-hook
[enable automatic linting]: /tools/lint/usage.html#using-a-vcs-hook

View File

@ -47,7 +47,7 @@ This enables `LogLevel::Debug` level information and places all
output in the file service.log in your current working directory.
[preference]: ./Prefs.html
[preference]: Prefs.md
[System observer notifications]: https://developer.mozilla.org/en-US/docs/Archive/Add-ons/Overlay_Extensions/XUL_School/Observer_Notifications
[prlog.h]: https://searchfox.org/mozilla-central/source/nsprpub/pr/include/prlog.h
[wiki]: https://wiki.mozilla.org/Remote/Developer_Resources

View File

@ -74,7 +74,7 @@ process interspersed with some tips.
up for review, run the Puppeteer test job on try again with `--rebuild 10`
to check for stability.
[Testing]: ../Testing.html
[Testing]: ../Testing.md
[Puppeteer test suite]: https://github.com/GoogleChrome/puppeteer/tree/master/test
[re-install the project]: https://github.com/puppeteer/puppeteer/blob/main/CONTRIBUTING.md#getting-code
[run tests against both Chromium and Firefox]: https://github.com/puppeteer/puppeteer/blob/main/test/README.md#running-tests

View File

@ -51,7 +51,7 @@ You may also opt out of building all the WebDriver specific components
[mozilla-unified]: https://mozilla-version-control-tools.readthedocs.io/en/latest/hgmozilla/unifiedrepo.html
[artifact builds]: https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Artifact_builds
[mozconfig]: ../build/buildsystem/mozconfigs.html
[mozconfig]: /build/buildsystem/mozconfigs.rst
[ccache]: https://ccache.samba.org/
[sccache]: https://github.com/mozilla/sccache
[Remote Agent]: ../remote/index.html
[Remote Agent]: /remote/index.rst

View File

@ -2,7 +2,7 @@ Contributing
============
If you are new to open source or to Mozilla, you might like this
[tutorial for new Marionette contributors](NewContributors.html).
[tutorial for new Marionette contributors](NewContributors.md).
We are delighted that you want to help improve Marionette!
Marionette means different a few different things, depending
@ -32,8 +32,8 @@ By participating in this project, you agree to abide by the Mozilla
[Community Participation Guidelines]. Here are some guidelines
for contributing high-quality and actionable bugs and code.
[_Marionette_]: ./index.html
[_geckodriver_]: ../../geckodriver/geckodriver
[_Marionette_]: ./index.rst
[_geckodriver_]: /testing/geckodriver/index.rst
[_webdriver_]: https://searchfox.org/mozilla-central/source/testing/webdriver/README.md
[WebDriver protocol]: https://w3c.github.io/webdriver/webdriver-spec.html#protocol
[XPCOM]: https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/Guide
@ -58,21 +58,20 @@ code in our [code style document], which we highly recommend you read.
[reach out to us]: ./index.html#communication
[mozilla-central]: https://searchfox.org/mozilla-central/source/remote/marionette/
[good first bugs]: https://codetribute.mozilla.org/projects/automation
[code style document]: CodeStyle.html
[code style document]: CodeStyle.md
Next steps
----------
* [Building](Building.html)
* [Debugging](Debugging.html)
* [Testing](Testing.html)
* [Patching](Patches.html)
* [Building](Building.md)
* [Debugging](Debugging.md)
* [Testing](Testing.md)
* [Patching](Patches.md)
Other resources
---------------
* [Code style](CodeStyle.html)
* [Internals](internals/)
* [New Contributor Tutorial](NewContributors.html)
* [Code style](CodeStyle.md)
* [New Contributor Tutorial](NewContributors.md)

View File

@ -63,13 +63,13 @@ need to download a Marionette client or use the in-tree client.
* [Download and setup the Marionette JS client][6]
* [Protocol definition][7]
[1]: ../../python/marionette_driver.html
[2]: ../../python/marionette_driver.html
[3]: ./PythonTests.html
[4]: ./Debugging.html
[1]: /python/marionette_driver.rst
[2]: /python/marionette_driver.rst
[3]: PythonTests.md
[4]: Debugging.md
[5]: https://developer.mozilla.org/en-US/docs/Marionette/Builds
[6]: https://github.com/mozilla-b2g/marionette_js_client
[7]: ./Protocol.html
[7]: Protocol.md
Bugs

View File

@ -36,7 +36,7 @@ Accounts, communication
someone may have answered you in the mean time.
5. If you're having trouble reaching us over Element, you are welcome to send an
email to our [mailing list](index.html#communication) instead. It's a good
email to our [mailing list](index.rst#communication) instead. It's a good
idea to include your Element nick in your email message.
[Element]: https://chat.mozilla.org
@ -48,7 +48,7 @@ Accounts, communication
Getting the code, running tests
-------------------------------
Follow the documentation on [Contributing](Contributing.html) to get a sense of
Follow the documentation on [Contributing](Contributing.md) to get a sense of
our projects, and which is of most interest for you. You will also learn how to
get the Firefox source code, build your custom Firefox build, and how to run the
tests.
@ -59,7 +59,7 @@ Work on bugs and get code review
Once you are familiar with the code of the test harnesses, and the tests you might
want to start with your first contribution. The necessary steps to submit and verify
your patches are laid out in [Patches.md](Patches.html).
your patches are laid out in [Patches](Patches.md).
Resources

View File

@ -30,4 +30,4 @@ But you can also schedule tests by selecting relevant jobs yourself:
[commit creation guidelines]: https://mozilla-version-control-tools.readthedocs.io/en/latest/devguide/contributing.html?highlight=phabricator#submitting-patches-for-review
[becoming a Mozilla committer]: https://www.mozilla.org/en-US/about/governance/policies/commit/
[Firefox CI]: https://treeherder.mozilla.org/
[try preset]: https://firefox-source-docs.mozilla.org/tools/try/presets.html
[try preset]: /tools/try/presets

View File

@ -42,5 +42,5 @@ on the same system. The effective port is written to the user
preference file when the server has started and is also logged to
stdout.
[Remote Agent Preferences]: ../../remote/Prefs.html
[Remote Agent Preferences]: /remote/Prefs.md

View File

@ -36,7 +36,7 @@ The test structure is illustrated here:
# code to execute after all tests are run
MarionetteTestCase.tearDown(self)
[remote protocol]: Protocol.html
[remote protocol]: Protocol.md
[unittest]: https://docs.python.org/2.7/library/unittest.html
[`setUp`]: https://docs.python.org/2.7/library/unittest.html#unittest.TestCase.setUp
[`setUpClass`]: https://docs.python.org/2.7/library/unittest.html#unittest.TestCase.setUpClass
@ -67,5 +67,5 @@ The full API documentation is found [here], but the key objects are:
* [`Marionette`]: client that speaks to Firefox.
[here]: ../../../python/marionette_driver.html
[`Marionette`]: ../../../python/marionette_driver.html#marionette_driver.marionette.Marionette
[here]: /python/marionette_driver.rst
[`Marionette`]: /python/marionette_driver.rst#marionette_driver.marionette.Marionette

View File

@ -57,7 +57,7 @@ In case you want to run the tests with another binary like [Firefox Nightly]:
When working on Marionette it is often useful to surface the stdout
from Gecko, which can be achieved using the `--gecko-log` option.
See <Debugging.html> for usage instructions, but the gist is that
See [Debugging](Debugging.md) for usage instructions, but the gist is that
you can redirect all Gecko output to stdout:
% ./mach marionette-test --gecko-log - TEST
@ -75,7 +75,7 @@ controlling the dimensions of the no-op virtual display. This is
similar to using Xvfb(1) which you may know from the X windowing system,
but has the additional benefit of also working on macOS and Windows.
[functional tests]: PythonTests.html
[functional tests]: PythonTests.md
[Firefox Nightly]: https://nightly.mozilla.org/
@ -132,7 +132,7 @@ Marionette when you connect manually:
You should see output like `{"applicationType":"gecko","marionetteProtocol":3}`
[headless mode]: https://developer.mozilla.org/en-US/Firefox/Headless_mode
[geckodriver]: /testing/geckodriver/geckodriver
[geckodriver]: /testing/geckodriver/index.rst
WPT functional tests
@ -179,7 +179,7 @@ One-click loaners
-----------------
Additionally, for debugging hard-to-reproduce test failures in CI,
one-click loaners from <Taskcluster.html> can be particularly useful.
one-click loaners from [Taskcluster](Taskcluster.md) can be particularly useful.
Out-of-tree testing
@ -188,7 +188,7 @@ Out-of-tree testing
All the above examples show tests running _in-tree_, with a local
checkout of _central_ and a local build of Firefox. It is also
possibly to run the Marionette tests _without_ a local build and
with a downloaded test archive from <Taskcluster.html>.
with a downloaded test archive from [Taskcluster](Taskcluster.md)
If you want to run tests from a downloaded test archive, you will
need to download the `target.common.tests.tar.gz` artifact attached to