When uploading changes to [Fuchsia's Gerrit instance](https://fuchsia-review.googlesource.com/),
there are various options that can change the behavior of presubmit.
These options are represented by special strings added to the commit message
of a change.

This page documents the options that can be used for Fuchsia presubmit.

## Buganizer issue options

These options control associated bugs in [Buganizer](https://issues.fuchsia.dev).

### Bug

`Bug: #` adds a comment on the given [Buganizer](https://issues.fuchsia.dev) issue
when a change is submitted.

For example:

    Bug: 372314445

The above line resulted in [this
comment](https://issues.fuchsia.dev/issues/372314445#comment11).

### Fixed / Fixes

`Fixed: #` (or `Fixes: #`) adds a comment, **and marks as "Fixed"** , the given
[Buganizer](https://issues.fuchsia.dev) issue when a change is submitted.

For example:

    Fixed: 297456438

The above line resulted in
[this comment](https://issues.fuchsia.dev/issues/297456438#comment3)
and status change on the issue.

## Dependent changes options

### Depends-on

`Depends-on: <other-change-id>` marks the change as depending on another change,
possibly in a separate repository.

The change with the `Depends-on` footer will
not be submittable until all dependencies have been submitted, and any
dependencies will also be patched in during presubmit testing.

For example:

    Depends-on: Idc82d1483b4be8480aaa87bb48af8d03cfa45858

## Test options

These options control how tests are executed.

### Multiply

`Multiply: <test name>` will run the given test multiple times.
This is helpful to confirm that specific tests are not flaky.
This applies to builders triggered by CQ as well as manually-triggered
builders started using the **Choose Tryjobs** dropdown.

For example:

    Multiply: socket-integration

The above line reruns the "socket-integration" test multiple times.

### Run-All-Tests

`Run-All-Tests: true` runs all tests, even if static analysis
marks them as unaffected by a change. This option is helpful when
making changes that can implicitly affect the entire system, such
as changes to the Zircon kernel, Component Framework, Test Manager,
or Diagnostics.

### Cq-Include-Trybots

`Cq-Include-Trybots <list>` runs the given builders as part of presubmit
for the change, in addition to the default set of presubmit builders.

For example:

    Cq-Include-Trybots: luci.fuchsia.try:fuchsia-coverage-absolute

The above line forces execution of `fuchsia-coverage-absolute`
along with the other jobs for presubmit.

Use the **Choose Tryjobs** dropdown in Gerrit to see the full set of
available builders.
[](https://issues.fuchsia.dev/issues/new?component=1439230&template=1881640&description=Issue+on:+https://fuchsia.dev/docs/development/source_code/commit_message_options.md "Report a bug or suggest improvements on this page") [](https://cs.opensource.google/fuchsia/fuchsia/+/main:docs/development/source_code/commit_message_options.md "View the source code of this page") [](https://ci.android.com/edit?repo=fuchsia/fuchsia/main&file=docs/development/source_code/commit_message_options.md&cloneRepo=fuchsia/fuchsia:refs/heads/main&fullPath=fuchsia/docs/development/source_code/commit_message_options.md "Edit the source code of this page")