- Sort Score
- Result 10 results
- Languages All
Results 1 - 2 of 2 for solution (0.14 sec)
-
.github/workflows/codeql-analysis.yml
env: # Set the DEVELOCITY_ACCESS_KEY so that Gradle Build Scans are generated DEVELOCITY_ACCESS_KEY: ${{ secrets.GRADLE_ENTERPRISE_ACCESS_KEY }} # Potential stop-gap solution for ReadTimeout issues with the Gradle Build Cache # https://gradle.slack.com/archives/CHDLT99C6/p1636477584059200 GRADLE_OPTS: -Dhttp.keepAlive=false - name: Compile with Gradle without Build Scan
Others - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu May 02 09:13:16 GMT 2024 - 4K bytes - Viewed (0) -
CONTRIBUTING.md
* Keep commits discrete. Avoid including multiple unrelated changes in a single commit. * Keep commits self-contained. Avoid spreading a single change across multiple commits. A single commit should make sense in isolation. ### Testing changes After making changes, you can test your code in 2 ways: 1. Run tests. - Run `./gradlew :<subproject>:quickTest` where `<subproject>` is the name of the subproject you've changed.
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)