bqschemaupdater rename field

gistfile1.txt

[cr go] proto $ (bqsu-addmissing)  bqschemaupdater -message "buildbucket.v2.Build" -table "cr-buildbucket-dev.builds.completed_BETA"
Updating table "cr-buildbucket-dev.builds.completed_BETA"
The following changes to the schema will be made:
================================================================================
--- Current
+++ New
@@ -126,8 +126,7 @@

        // Gerrit patchsets to run against.
        // Usually present in tryjobs, set by CQ, Gerrit, git-cl-try.
-       // Applied on top of the corresponding commit in gitiles_commits
-       // or tip of the tree if the commit is not specified.
+       // Applied on top of gitiles_commit if specified, otherwise tip of the tree.
        //
        // V1 equivalent: supersedes patch_* properties and "buildset"
        // tag that starts with "patch/gerrit/".
@@ -143,6 +142,28 @@

                // Gerrit project, e.g. "chromium/src".
                STRING project
+       }
+
+       // Gitiles commits to run against.
+       // Usually present in CI builds, set by LUCI Scheduler.
+       // If not present, the build may checkout "refs/heads/master".
+       // NOT a blamelist.
+       //
+       // V1 equivalent: supersedes "revision" property and "buildset"
+       // tag that starts with "commit/gitiles/".
+       RECORD gitiles_commit {
+               // Gitiles hostname, e.g. "chromium.googlesource.com".
+               STRING host
+
+               // Commit HEX SHA1.
+               STRING id
+
+               // Repository name on the host, e.g. "chromium/src".
+               STRING project
+
+               // Optional, associated git ref, e.g. "refs/heads/master".
+               // NOT a branch name: if specified, must start with "refs/".
+               STRING ref
        }

        // Gitiles commits to run against.

================================================================================
Continue? [y/N]