- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for Every (0.14 sec)
-
CONTRIBUTING.md
3. Pull requests are not merged directly into the master branch. 4. Code contributions require signing a Google CLA. API changes ----------- We make changes to Guava's public [APIs][], including adding new APIs, very carefully. Because of this, if you're interested in seeing a new feature in Guava, the best approach is to create an [issue][] (or comment on an existing issue if there is one) requesting the feature and describing specific use cases
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) -
CONTRIBUTING.md
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. If you run the sanity check locally with the `./gradlew sanityCheck`, you can see the binary compatibility error in the output. It looks like the following: ```
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) -
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
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)