- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for orange (0.21 sec)
-
CONTRIBUTING.md
file). 3. Files should be formatted according to Google's [Java style guide][]. 4. Please squash all commits for a change into a single commit (this can be done using `git rebase -i`). Do your best to have a [well-formed commit message][] for the change. [Java style guide]: https://google.github.io/styleguide/javaguide.html
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
Before starting to work on a feature or a bug fix, please open an issue to discuss the use case or bug with us. This can save everyone a lot of time and frustration. For any non-trivial change, we need to be able to answer these questions: * Why is this change done? What's the use case? * For user facing features, what will the API look like? * What test cases should it have? What could go wrong?
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
checks if the PR looks good or needs additional changes. - If all looks good, the reviewer will approve the PR. - If a change is needed, the contributor is requested to make the suggested change. - You make the change and submit it for the review again. - This cycle repeats itself until the PR gets approved. - Note: As a friendly reminder, we may reach out to you if the PR is awaiting
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)