- Sort Score
- Result 10 results
- Languages All
Results 1 - 7 of 7 for suivre (0.2 sec)
-
CONTRIBUTING.md
License Agreement. This is not a copyright _assignment_; it simply gives Google permission to use and redistribute your contributions as part of the project. - If you are an individual writing original source code and you're sure you own the intellectual property, then you'll need to sign an [individual CLA][]. Please include your GitHub username. - If you work for a company that wants to allow you to contribute your work,
Plain Text - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Fri Nov 17 18:47:47 GMT 2023 - 3.7K bytes - Viewed (0) -
CONTRIBUTING.md
Getting Started --------------- + Make sure you have a [JIRA account](https://issues.apache.org/jira/). + Make sure you have a [GitHub account](https://github.com/signup/free). + If you're planning to implement a new feature, it makes sense to discuss your changes on the [dev list](https://maven.apache.org/mailing-lists.html) first. This way you can make sure you're not wasting your time on something that isn't
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
#### Import Gradle into IntelliJ To import Gradle into IntelliJ: - Open the `build.gradle.kts` file with IntelliJ and choose "Open as Project" - Make sure "Create separate module per source set" is selected - Make sure "Use default gradle wrapper" is selected - Select a Java 11 VM as "Gradle JVM" - In the "File already exists" dialogue, choose "Yes" to overwrite
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
# Contributing guidelines ## Pull Request Checklist Before sending your pull requests, make sure you do the following: - Read the [contributing guidelines](CONTRIBUTING.md). - Read the [Code of Conduct](CODE_OF_CONDUCT.md). - Ensure you have signed the [Contributor License Agreement (CLA)](https://cla.developers.google.com/). - Check if your changes are consistent with the
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) -
.github/CONTRIBUTING.md
forking the repository and sending a pull request. When submitting code, please make every effort to follow existing conventions and style in order to keep the code as readable as possible. Please also make sure your code compiles by running `./gradlew check`. Checkstyle failures during compilation indicate errors in your style and can be viewed in the `checkstyle-result.xml` file. Some general advice
Plain Text - Registered: Fri Apr 26 11:42:10 GMT 2024 - Last Modified: Sun Mar 17 04:16:26 GMT 2019 - 1.4K 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 - To add test cases for the new code. If you have questions about how to do it, please ask on our [Slack](https://slack.min.io) channel.
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
See the [security policy](https://golang.org/security) for details. The recommended way to file an issue is by running `go bug`. Otherwise, when filing an issue, make sure to answer these five questions: 1. What version of Go are you using (`go version`)? 2. What operating system and processor architecture are you using? 3. What did you do? 4. What did you expect to see?
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)