- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for or (0.34 sec)
-
CONTRIBUTING.md
start by opening a new issue describing the bug or feature you're intending to fix. Even if you think it's relatively minor, it's helpful to know what people are working on. And as mentioned above, API changes should be discussed thoroughly before moving to code. Some examples of types of pull requests that are immediately helpful: - Fixing a bug without changing a public API. - Fixing or improving documentation.
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
* maximize the chance of your changes being accepted * work on the Gradle code base * get help if you encounter trouble ## Before you start 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?
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
- If the PR didn't meet the validation criteria, we request for additional changes to be made to PR to pass quality checks and send it back or on a rare occasion we may reject it. **3. Review** - For a valid PR, reviewer (person familiar with the code/functionality) checks if the PR looks good or needs additional changes. - If all looks good, the reviewer will approve the PR.
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)