Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 4 of 4 for live (0.21 sec)

  1. CONTRIBUTING.md

    pull requests directly into the master branch. Instead, once a pull request is
    ready for merging, we'll make the appropriate changes in the internal codebase
    and, when the change is synced out, give the pull request author credit for the
    commit.
    
    Contributor License Agreement
    -----------------------------
    
    Contributions to any Google project must be accompanied by a Contributor
    Plain Text
    - Registered: Fri May 03 12:43:13 GMT 2024
    - Last Modified: Fri Nov 17 18:47:47 GMT 2023
    - 3.7K bytes
    - Viewed (0)
  2. CONTRIBUTING.md

     limitations under the License.
    -->
    Contributing to Apache Maven
    ======================
    
    You have found a bug or you have an idea for a cool new feature? Contributing
    code is a great way to give something back to the open source community. Before
    you dig right into the code, there are a few guidelines that we need
    contributors to follow so that we can have a chance of keeping on top of
    things.
    
    Plain Text
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Sun Oct 10 09:48:27 GMT 2021
    - 4.7K bytes
    - Viewed (0)
  3. .github/CONTRIBUTING.md

    Contributing
    ============
    
    If you would like to contribute code to OkHttp you can do so through GitHub by
    forking the repository and sending a pull request.
    
    When submitting code, please make every effort to follow existing conventions
    and style in order to keep the code as readable as possible. Please also make
    sure your code compiles by running `./gradlew check`. Checkstyle failures
    during compilation indicate errors in your style and can be viewed in the
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Sun Mar 17 04:16:26 GMT 2019
    - 1.4K bytes
    - Viewed (0)
  4. CONTRIBUTING.md

    See the [security policy](https://golang.org/security) for details.
    
    The recommended way to file an issue is by running `go bug`.
    Otherwise, when filing an issue, make sure to answer these five questions:
    
    1. What version of Go are you using (`go version`)?
    2. What operating system and processor architecture are you using?
    3. What did you do?
    4. What did you expect to see?
    5. What did you see instead?
    
    Plain Text
    - Registered: Tue May 07 11:14:38 GMT 2024
    - Last Modified: Wed Mar 29 22:00:27 GMT 2023
    - 1.3K bytes
    - Viewed (0)
Back to top