1<!-- 2 Copyright 2022 Google LLC. All rights reserved. 3 4 Licensed under the Apache License, Version 2.0 (the License); 5 you may not use this file except in compliance with the License. 6 You may obtain a copy of the License at 7 8 http://www.apache.org/licenses/LICENSE-2.0 9 10 Unless required by applicable law or agreed to in writing, software 11 distributed under the License is distributed on an "AS IS" BASIS, 12 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 13 See the License for the specific language governing permissions and 14 limitations under the License. 15--> 16 17Want to contribute? Great! First, read this page (including the small print at 18the end). 19 20### Before you contribute 21**Before we can use your code, you must sign the 22[Google Individual Contributor License Agreement](https://developers.google.com/open-source/cla/individual?csw=1) 23(CLA)**, which you can do online. 24 25The CLA is necessary mainly because you own the copyright to your changes, 26even after your contribution becomes part of our codebase, so we need your 27permission to use and distribute your code. We also need to be sure of 28various other things — for instance that you'll tell us if you know that 29your code infringes on other people's patents. You don't have to sign 30the CLA until after you've submitted your code for review and a member has 31approved it, but you must do it before we can put your code into our codebase. 32 33### The small print 34Contributions made by corporations are covered by a different agreement than 35the one above, the 36[Software Grant and Corporate Contributor License Agreement](https://cla.developers.google.com/about/google-corporate). 37 38### Contribution process 39 401. Explain your idea and discuss your plan with members of the team. The best 41 way to do this is to create 42 an [issue](https://github.com/bazelbuild/rules_kotlin/issues) or comment on 43 an existing issue. 441. Prepare a git commit with your change. Don't forget to 45 add [tests](https://github.com/bazelbuild/rules_kotlin/tree/main/tests). 46 Run the existing tests with `bazel test //...`. Update 47 [README.md](https://github.com/bazelbuild/rules_kotlin/blob/main/README.md) 48 if appropriate. 491. [Create a pull request](https://help.github.com/articles/creating-a-pull-request/). 50 This will start the code review process. **All submissions, including 51 submissions by project members, require review.** 521. You may be asked to make some changes. You'll also need to sign the CLA at 53 this point, if you haven't done so already. Our continuous integration bots 54 will test your change automatically on supported platforms. Once everything 55 looks good, your change will be merged. 56