- Sort Score
- Result 10 results
- Languages All
Results 1 - 7 of 7 for Oranges (0.28 sec)
-
CONTRIBUTING.md
things you should know about contributing: 1. API changes require discussion, use cases, etc. Code comes later. 2. Pull requests are great for small fixes for bugs, documentation, etc. 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
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
2. Accept the changes.\ If you are sure that the changes are intentional, follow the steps described in the report. This includes adding the description of the changes to the `accepted-public-api-changes.json` file, and providing a reason for each change. You can add the changes to any place in the file, e.g. at the top. 3. Make sure the file with accepted changes is sorted.\
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Fri Feb 09 15:30:53 GMT 2024 - 15.6K bytes - Viewed (0) -
CONTRIBUTING.md
Making and Submitting Changes -------------- We accept Pull Requests via GitHub. The [developer mailing list][dev-ml-list] is the main channel of communication for contributors. There are some guidelines which will make applying PRs easier for us: + Create a topic branch from where you want to base your work (this is usually the master branch). Push your changes to a topic branch in your fork of the repository.
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Oct 10 09:48:27 GMT 2021 - 4.7K bytes - Viewed (0) -
CONTRIBUTING.md
$ git fetch upstream $ git merge upstream/master ... ``` ### Create your feature branch Before making code changes, make sure you create a separate branch for these changes ``` git checkout -b my-new-feature ``` ### Test MinIO server changes After your code changes, make sure
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Sat Feb 12 00:51:25 GMT 2022 - 2.8K bytes - Viewed (0) -
CONTRIBUTING.md
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? For change proposals, see [Proposing Changes To Go](https://go.dev/s/proposal-process). ## Contributing code Please read the [Contribution Guidelines](https://golang.org/doc/contribute.html) before sending patches.
Plain Text - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Wed Mar 29 22:00:27 GMT 2023 - 1.3K bytes - Viewed (0) -
CONTRIBUTING.md
``` ./gradlew clean check ``` Please make every effort to follow existing conventions and style in order to keep the code as readable as possible. Contribute code changes through GitHub by forking the repository and sending a pull request. We squash all pull requests on merge. Gradle Setup ------------ ``` $ cat local.properties sdk.dir=PATH_TO_ANDROID_HOME/sdk
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) -
CONTRIBUTING.md
- Ensure you have signed the [Contributor License Agreement (CLA)](https://cla.developers.google.com/). - Check if your changes are consistent with the [guidelines](#general-guidelines-and-philosophy-for-contribution). - Changes are consistent with the [Coding Style](#c-coding-style). - Run the [unit tests](#running-unit-tests). ## How to become a contributor and submit your own code
Plain Text - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Thu Mar 21 11:45:51 GMT 2024 - 15.6K bytes - Viewed (0)