tree a4638fcc10cb57ff1872d30d28ed605641aca0d3
parent a59037bda96e17c4073d45079e1e2be7d13600eb
author Youssef Elghareeb <ghareeb@google.com> 1599162990 +0200
committer Youssef Elghareeb <ghareeb@google.com> 1599736277 +0200

Add the work_in_progress option to the revert and revertSubmission endpoints

Sometimes bots want to validate whether a change break a build/tests by
creating a revert of a change and validating it. Unless the revert fixes
the breakage, it won't need to notify the author of the original change
and/or get reviewed. This notification can cause panic to the former
author.

This change adds a work in progress (WIP) field to the RevertInput that
can be used for testing purposes where reviewers get notified only if we
determine we want to move forward with the revert.

CherryPickChange was also modified with a WIP parameter. Cherry picking
is used by revert submission (the first revert is created normally on
top of the branch tip, subsequent reverts are cherry picked). The
modifications done to CherryPickChange in this change are only used by
RevertSubmission and do not affect the serving path of the cherry pick
endpoint.

Bug: Issue 13357
Change-Id: Ida96151e1bed8d62f19510681154f8940df8e58d