Lines Matching +full:test +full:- +full:cl

1 ---
4 ---
8 <!--?prettify lang=sh?-->
10     git config --global user.name "Your Name"
11     git config --global user.email you@example.com
17 <!--?prettify lang=sh?-->
20     git checkout -b my_feature origin/main
24 <!--?prettify lang=sh?-->
31 <!--?prettify lang=sh?-->
34     python2 tools/git-sync-deps
36 ## Adding a unit test
38 If you are willing to change Skia codebase, it's nice to add a test at the same
41 Test code is located under the 'tests' directory.
46 an automated way to verify the results, consider writing a GM test. Also, if
48 standard unit test suite, but there are GPU-specific testing paths you can
54 [Individual Contributor License Agreement](http://code.google.com/legal/individual-cla-v1.0.html).
57 [Corporate Contributor License Agreement](http://code.google.com/legal/corporate-cla-v1.0.html)
59 name and contact info to the AUTHORS file as a part of your CL.
61 Now that you've made a change and written a test for it, it's ready for the code
64 Use `git-cl`, which comes with
65 [depot tools](http://sites.google.com/a/chromium.org/dev/developers/how-tos/install-depot-tools).
66 For help, run `git cl help`. Note that in order for `git cl` to work correctly,
69 `git cl` usage.
78 <img src="/docs/dev/contrib/SuggestedReviewers.png" style="display: inline-block; max-width: 75%" />
83 [skia-review](http://skia-review.googlesource.com). Use `git cl` to upload your
86 <!--?prettify lang=sh?-->
88     git cl upload
93 `git config --global user.email` above, but it can.
96 (https://skia-review.googlesource.com/c/4559/), indicating where your changelist
103 ask a committer. After uploading your CL to
104 [Gerrit](https://skia-review.googlesource.com/), you may trigger a try job for
105 any job listed in tasks.json, either via the Gerrit UI, using `git cl try`, eg.
107     git cl try -B skia.primary -b Some-Tryjob-Name
109 or using bin/try, a small wrapper for `git cl try` which helps to choose try
112     bin/try --list
116     bin/try "Test.*GTX660.*Release"
130 in the upper right. _Hint_: You can add -r reviewer@example.com --send-mail to
131 send the email directly when uploading a change using `git-cl`.
146 that it is updating the current CL and ask you for a message explaining the
150 If you need to update code the code on an already uploaded CL, simply edit the
151 code, commit it again locally, and then run git cl upload again e.g.
155     git commit -m 'add GOATS fix to whitespace.txt'
156     git cl upload
161 approve your change by setting the Code-Review label to "+1".
172     git checkout -q origin/main
173     git branch -D my_feature
179 expected to test for and alleviate this. You may be able to find a Skia team
188 your friendly Skia-Blink engineer to evaluate, rebaseline, and land your
193 [How to land Skia changes that change Blink layout test results](/docs/dev/chrome/blink/)
201 ### Non-Skia-committers
218 - tips on how to apply an externally provided patch are [here](../patch)
219 - when landing externally contributed patches, please note the original
223   `git-cl` will squash all your commits into a single one with the description
227   git cl land
233   git cl land -c 'Contributor Name <email@example.com>'