diff options
| author | thakis <thakis@chromium.org> | 2015-02-23 09:00:37 -0800 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-02-23 17:01:24 +0000 |
| commit | 4f02f4cd6c8b9087ecd286c905b15e253d88d82f (patch) | |
| tree | ddddecc466cd4ac08007913660bddebae1c3f77f /ui/keyboard | |
| parent | 6377bfd717ccf6488462d6d22248f28918c247b5 (diff) | |
| download | chromium_src-4f02f4cd6c8b9087ecd286c905b15e253d88d82f.zip chromium_src-4f02f4cd6c8b9087ecd286c905b15e253d88d82f.tar.gz chromium_src-4f02f4cd6c8b9087ecd286c905b15e253d88d82f.tar.bz2 | |
Make `git cl try` to the same as hitting cq (except for presubmit).
PRESUBMIT.py used to contain a handwritten list of bots to trigger on
`git cl try`. It was always out of sync with what the cq did.
https://codereview.chromium.org/823823002 awesomely made `git cl try` do
the same thing as the commit queue, but it kept a few special-case rules around.
It's better to not have these special cases: Once the developer hits cq, all
the "intelligently" skipped bots need to be run anyways. More importantly,
there should be only one system to decide what to run and it should be
identical for cq and `git cl try`. Currently, we think this system is the
`analyze` step, and it does a decent job of that already.
BUG=none (but made possible by 443613)
Review URL: https://codereview.chromium.org/921323003
Cr-Commit-Position: refs/heads/master@{#317597}
Diffstat (limited to 'ui/keyboard')
0 files changed, 0 insertions, 0 deletions