Directly committing code

Contents

    No headings.

    When contributing code to Chromium, the last step in the life of a change list is committing it, after which it's closed.

    The preferred way of committing changes is via the commit queue.

    However, in certain circumstances it is acceptable or necessary to directly commit your change, bypassing the commit queue. This is discouraged however, due to not running the tests (hence higher risk of breakage), and requires more supervision on the part of the committer.

    Updated instructions for bypassing the commit queue are here:
    Comments