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     python3 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
61 [`select`](https://bazel.build/reference/be/common-definitions#configurable-attributes) statements
67 [Individual Contributor License Agreement](http://code.google.com/legal/individual-cla-v1.0.html).
70 [Corporate Contributor License Agreement](http://code.google.com/legal/corporate-cla-v1.0.html)
72 name and contact info to the AUTHORS file as a part of your CL.
74 Now that you've made a change and written a test for it, it's ready for the code
77 Use `git-cl`, which comes with
78 [depot tools](http://sites.google.com/a/chromium.org/dev/developers/how-tos/install-depot-tools).
79 For help, run `git cl help`. Note that in order for `git cl` to work correctly,
82 `git cl` usage.
91 <img src="/docs/dev/contrib/SuggestedReviewers.png" style="display: inline-block; max-width: 75%" />
96 [skia-review](http://skia-review.googlesource.com). Use `git cl` to upload your
99 <!--?prettify lang=sh?-->
101     git cl upload
106 `git config --global user.email` above, but it can.
109 ([https://skia-review.googlesource.com/c/4559/](https://skia-review.googlesource.com/c/4559/)),
116 ask a committer. After uploading your CL to
117 [Gerrit](https://skia-review.googlesource.com/), you may trigger a try job for
118 any job listed in tasks.json, either via the Gerrit UI, using `git cl try`, eg.
120     git cl try -B skia.primary -b Some-Tryjob-Name
122 or using bin/try, a small wrapper for `git cl try` which helps to choose try
125     bin/try --list
129     bin/try "Test.*GTX660.*Release"
143 in the upper right. _Hint_: You can add -r reviewer@example.com --send-mail to
144 send the email directly when uploading a change using `git-cl`.
159 that it is updating the current CL and ask you for a message explaining the
163 If you need to update code the code on an already uploaded CL, simply edit the
164 code, commit it again locally, and then run git cl upload again e.g.
168     git commit -m 'add GOATS fix to whitespace.txt'
169     git cl upload
174 approve your change by setting the Code-Review label to "+1".
185     git checkout -q origin/main
186     git branch -D my_feature
192 expected to test for and alleviate this. You may be able to find a Skia team
201 your friendly Skia-Blink engineer to evaluate, rebaseline, and land your
206 [How to land Skia changes that change Blink layout test results](/docs/dev/chrome/blink/)
214 ### Non-Skia-committers
231 - tips on how to apply an externally provided patch are [here](../patch)
232 - when landing externally contributed patches, please note the original
236   `git-cl` will squash all your commits into a single one with the description
240   git cl land
246   git cl land -c 'Contributor Name <email@example.com>'