mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-08 10:44:56 +00:00
no bug - Fix a rst mistake, causing the note to be displayed r=marco DONTBUILD
Depends on D75260 Differential Revision: https://phabricator.services.mozilla.com/D75261
This commit is contained in:
parent
d11275bd72
commit
713c6207e3
@ -31,7 +31,7 @@ Python function of your devising.
|
|||||||
Creating a Callback Action
|
Creating a Callback Action
|
||||||
--------------------------
|
--------------------------
|
||||||
|
|
||||||
.. note:
|
.. note::
|
||||||
|
|
||||||
You can generate ``actions.json`` on the command line with ``./mach taskgraph actions``.
|
You can generate ``actions.json`` on the command line with ``./mach taskgraph actions``.
|
||||||
|
|
||||||
|
@ -43,7 +43,7 @@ But we can configure mac-only files such as ``CoreLocationLocationProvider.mm``
|
|||||||
It is also possible to define a file as affecting an inclusive component and nothing else.
|
It is also possible to define a file as affecting an inclusive component and nothing else.
|
||||||
For example, the source code and configuration for the Python linting tasks does not affect any tasks other than linting.
|
For example, the source code and configuration for the Python linting tasks does not affect any tasks other than linting.
|
||||||
|
|
||||||
.. note:
|
.. note::
|
||||||
|
|
||||||
Most unit test suite tasks are allocated to components for their platform family and for the test suite.
|
Most unit test suite tasks are allocated to components for their platform family and for the test suite.
|
||||||
This indicates that if a platform family is affected (for example, ``android``) then the builds for that platform should execute as well as the full test suite.
|
This indicates that if a platform family is affected (for example, ``android``) then the builds for that platform should execute as well as the full test suite.
|
||||||
|
@ -35,7 +35,7 @@ the target task set is almost the entire task graph, so targeted tasks are
|
|||||||
considered for optimization. This behavior is controlled with the
|
considered for optimization. This behavior is controlled with the
|
||||||
``optimize_target_tasks`` parameter.
|
``optimize_target_tasks`` parameter.
|
||||||
|
|
||||||
.. note:
|
.. note::
|
||||||
|
|
||||||
Because it is a mix of "what the push author wanted" and "what should run
|
Because it is a mix of "what the push author wanted" and "what should run
|
||||||
when necessary", try pushes with the old option syntax (``-b do -p all``,
|
when necessary", try pushes with the old option syntax (``-b do -p all``,
|
||||||
|
@ -52,7 +52,7 @@ incompatible as to be harmful. For example, some changes to filter expression
|
|||||||
handling cannot be detected by filter expressions, and so older clients that
|
handling cannot be detected by filter expressions, and so older clients that
|
||||||
receive filters using these new features would break.
|
receive filters using these new features would break.
|
||||||
|
|
||||||
.. note:
|
.. note::
|
||||||
|
|
||||||
Capabilities were first introduced in Firefox 70. Clients prior to this
|
Capabilities were first introduced in Firefox 70. Clients prior to this
|
||||||
do not check capabilities, and run all recipes provided. To accommodate
|
do not check capabilities, and run all recipes provided. To accommodate
|
||||||
|
Loading…
Reference in New Issue
Block a user