- Sort Score
- Result 10 results
- Languages All
Results 1 - 4 of 4 for beste (0.25 sec)
-
Development.md
# Development best practices This is a collection of best practices for Gradle implementation. Should and should not do's. ## Error messages and suggestions Traditionally, if an error occurred, the error message and the possible solution were provided to the console via a single String in the corresponding exception. That meant possible solutions for Problems could be scattered all over the console output.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Tue Feb 06 22:54:40 GMT 2024 - 1.8K bytes - Viewed (0) -
README.md
</picture> [![Revved up by Develocity](https://img.shields.io/badge/Revved%20up%20by-Develocity-06A0CE?logo=Gradle&labelColor=02303A)](https://ge.gradle.org/scans) [![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/4898/badge)](https://bestpractices.coreinfrastructure.org/projects/4898)
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sun Mar 24 20:49:08 GMT 2024 - 3.9K bytes - Viewed (0) -
architecture/standards/0001-use-architectural-decision-records.md
# ADR-0001 - Use Architectural Decision Records ## Date 2023-12-01 ## Context In a distributed team with many subteams, the best solution to communicate decisions is to use a format accessible by everyone in charge of development. We use *Specification* and *Discovery* documents stored in Google Drive, but they present some downsides:
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sat Mar 02 21:54:40 GMT 2024 - 2.8K bytes - Viewed (0) -
.cm/code_experts.cm
# its own file. on: - pr_created - commit - comment_added automations: # Also post a comment that lists the best experts for the files that were modified. comment_experts: if: - {{ ('code_experts' | isEnabledAutomation(pr)) }} run: - action: explain-code-experts@v1 args:
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 1.3K bytes - Viewed (0)