Problem Statement

There are lots of things you would want to do in a pull request involving diffs and history! For example, you might want to make sure all new changes pass a linter, but it would be impossible to know what new changes are for the entire pull request without a full knowledge of the diff.

Proposed Solution

The cloned git repository should clone down at at least the base revision from when the pull request diverged from the main branch so that diff analysis can be easily done. Ideally it will also include a reference to the merge target as well. Ideally, well-documented git commands from the cloud build yaml will describe how to switch branches using the injected substitutions.

Related Issues

• https://issuetracker.google.com/issues/285169029
• https://issuetracker.google.com/issues/119662038