Don't run git add/rm after rebaseline commands for rebaseline-cl.

third_party/WebKit/Tools/Scripts/webkitpy/tool/commands/rebaseline_cl.py

Index: third_party/WebKit/Tools/Scripts/webkitpy/tool/commands/rebaseline_cl.py
diff --git a/third_party/WebKit/Tools/Scripts/webkitpy/tool/commands/rebaseline_cl.py b/third_party/WebKit/Tools/Scripts/webkitpy/tool/commands/rebaseline_cl.py
index eb72502cd108ab61d7eb80ff25522db553858d9e..c58b38bb2ebbba971412f99bd9f73b4602fddbf6 100644
--- a/third_party/WebKit/Tools/Scripts/webkitpy/tool/commands/rebaseline_cl.py
+++ b/third_party/WebKit/Tools/Scripts/webkitpy/tool/commands/rebaseline_cl.py
@@ -66,7 +66,7 @@ class RebaselineCL(AbstractParallelRebaselineCommand):
 
         if options.dry_run:
             return
-        self._rebaseline(options, test_prefix_list)
+        self._rebaseline(options, test_prefix_list, update_scm=False)

[wkorman, 2016/08/19 22:54:07]

So in terms of addressing the bug, after this change, what is the behavior?
Nothing will be auto-staged for the developer, but they'll see newly
pulled/optimized baselines in their directory and can manually add them? Just
want to make sure I am following re: this patch and the bug.

[qyearsley, 2016/08/19 23:32:27]

Right, exactly. Changes will be made but not staged. So, if you run webkit-patch
rebaseline-cl and it modifies an existing CL, you can still commit your changes
with `git commit -a`, but if you're adding a new baseline, you must `git add`
the new file before committing.

This may be an extra step, but it's less confusing than the current behavior,
where `git status` shows a bunch of files being both added and deleted.

 
     def _get_issue_number(self, options):
         """Gets the Rietveld CL number from either |options| or from the current local branch."""