Lines Matching +full:test +full:- +full:cl
6 -------------
8 <!--?prettify lang=sh?-->
10 git config --global user.name "Your Name"
11 git config --global user.email you@example.com
14 --------------
18 <!--?prettify lang=sh?-->
21 git checkout -b my_feature origin/master
25 <!--?prettify lang=sh?-->
32 <!--?prettify lang=sh?-->
35 python2 tools/git-sync-deps
37 Adding a unit test
38 ------------------
40 If you are willing to change Skia codebase, it's nice to add a test at the same
43 Test code is located under the 'tests' directory.
48 an automated way to verify the results, consider writing a GM test. Also, if your
50 unit test suite, but there are GPU-specific testing paths you can extend.
53 ------------------
57 Agreement](http://code.google.com/legal/individual-cla-v1.0.html). You can do
60 Agreement](http://code.google.com/legal/corporate-cla-v1.0.html)
62 name and contact info to the AUTHORS file as a part of your CL.
64 Now that you've made a change and written a test for it, it's ready for the code
67 Use `git-cl`, which comes with [depot
68 tools](http://sites.google.com/a/chromium.org/dev/developers/how-tos/install-depot-tools).
69 For help, run `git cl help`.
79 Skia uses the Gerrit code review tool. Skia's instance is [skia-review](http://skia-review.googleso…
80 Use `git cl` to upload your change:
82 <!--?prettify lang=sh?-->
84 git cl upload
89 configured using `git config --global user.email` above, but it can.
92 (https://skia-review.googlesource.com/c/4559/), indicating where your changelist
99 ask a committer. After uploading your CL to [Gerrit](https://skia-review.googlesource.com/),
101 Gerrit UI, using `git cl try`, eg.
103 git cl try -B skia.primary -b Some-Tryjob-Name
105 or using bin/try, a small wrapper for `git cl try` which helps to choose try jobs.
108 bin/try --list
112 bin/try "Test.*GTX660.*Release"
126 in the upper right. _Hint_: You can add -r reviewer@example.com --send-mail to
127 send the email directly when uploading a change using `git-cl`.
131 ------------------
144 that it is updating the current CL and ask you for a message explaining the
148 If you need to update code the code on an already uploaded CL, simply edit the
149 code, commit it again locally, and then run git cl upload again e.g.
153 git commit -m 'add GOATS fix to whitespace.txt'
154 git cl upload
159 approve your change by setting the Code-Review label to "+1".
169 git checkout -q origin/master
170 git branch -D my_feature
174 -------------
178 expected to test for and alleviate this. You may be able to find a Skia team
187 your friendly Skia-Blink engineer to evaluate, rebaseline, and land your
192 [How to land Skia changes that change Blink layout test results](../chrome/layouttest)
199 ---------------------
201 ### Non-Skia-committers
221 …`git-cl` will squash all your commits into a single one with the description you used when you upl…
224 git cl land
230 git cl land -c 'Contributor Name <email@example.com>'