github.com/bazelbuild/bazel-gazelle@v0.36.1-0.20240520142334-61b277ba6fed/CONTRIBUTING.md (about)

     1  Want to contribute? Great! First, read this page (including the small print at
     2  the end).
     3  
     4  ### Before you contribute
     5  **Before we can use your code, you must sign the
     6  [Google Individual Contributor License Agreement](https://developers.google.com/open-source/cla/individual?csw=1)
     7  (CLA)**, which you can do online.
     8  
     9  The CLA is necessary mainly because you own the copyright to your changes,
    10  even after your contribution becomes part of our codebase, so we need your
    11  permission to use and distribute your code. We also need to be sure of
    12  various other things — for instance that you'll tell us if you know that
    13  your code infringes on other people's patents. You don't have to sign
    14  the CLA until after you've submitted your code for review and a member has
    15  approved it, but you must do it before we can put your code into our codebase.
    16  
    17  ### The small print
    18  Contributions made by corporations are covered by a different agreement than
    19  the one above, the
    20  [Software Grant and Corporate Contributor License Agreement](https://cla.developers.google.com/about/google-corporate).
    21  
    22  ### Contribution process
    23  
    24  1. Explain your idea and discuss your plan with members of the team. The best
    25     way to do this is to create
    26     an [issue](https://github.com/bazelbuild/bazel-gazelle/issues) or comment on an
    27     existing issue.
    28  1. Prepare a git commit with your change. Don't forget to
    29     add [tests](https://github.com/bazelbuild/bazel-gazelle/tree/master/tests). 
    30     Run the existing tests with `bazel test //...`. Update
    31     [README.rst](https://github.com/bazelbuild/bazel-gazelle/blob/master/README.rst)
    32     if appropriate.
    33  1. [Create a pull request](https://help.github.com/articles/creating-a-pull-request/).
    34     This will start the code review process. **All submissions, including
    35     submissions by project members, require review.**
    36  1. You may be asked to make some changes. You'll also need to sign the CLA at
    37     this point, if you haven't done so already. Our continuous integration bots
    38     will test your change automatically on supported platforms. Once everything
    39     looks good, your change will be merged.