Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for PR (0.13 sec)

  1. CONTRIBUTING.md

    `git push --force origin test-branch`
    
    ### Fixing sanity check failures after public API changes
    
    If your PR includes any changes to the Gradle Public API, it will cause the binary compatibility check to fail.
    The binary compatibility check runs as a part of the broader sanity check.
    The latter runs on every PR and is a prerequisite for merging.
    
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Sat May 04 07:43:02 GMT 2024
    - 15.6K bytes
    - Viewed (0)
  2. CONTRIBUTING.md

    ### Typical Pull Request Workflow -
    
    **1. New PR**
    
    - As a contributor, you submit a New PR on GitHub.
    - We inspect every incoming PR and add certain labels to the PR such as `size:`,
      `comp:` etc.  At this stage we check if the PR is valid and meets certain
      quality requirements. For example, we check if the CLA is signed, PR has
      sufficient description, if applicable unit tests are added, if it is a
    Plain Text
    - Registered: Tue May 07 12:40:20 GMT 2024
    - Last Modified: Thu Mar 21 11:45:51 GMT 2024
    - 15.6K bytes
    - Viewed (0)
  3. CONTRIBUTING.md

    [Individual Contributor License Agreement (CLA)][cla].
    
    
    Code Contributions
    ------------------
    
    Get working code on a personal branch with tests passing before you submit a PR:
    
    ```
    ./gradlew clean check
    ```
    
    Please make every effort to follow existing conventions and style in order to keep the code as
    readable as possible.
    
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Tue Feb 14 08:26:50 GMT 2023
    - 2K bytes
    - Viewed (0)
Back to top