- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 26 for commit1 (0.21 sec)
-
.github/PULL_REQUEST_TEMPLATE.md
### Contributor Checklist - [ ] [Review Contribution Guidelines](https://github.com/gradle/gradle/blob/master/CONTRIBUTING.md). - [ ] Make sure that all commits are [signed off](https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---signoff) to indicate that you agree to the terms of [Developer Certificate of Origin](https://developercertificate.org/).
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Tue Feb 13 22:36:19 GMT 2024 - 1.7K bytes - Viewed (0) -
.teamcity/src/main/kotlin/model/CIBuildModel.kt
val channel: String, val extraParameters: String = "" ) { per_commit( displayName = "Performance Regression Test", timeout = 420, channel = "commits" ), per_day( displayName = "Slow Performance Regression Test", timeout = 420, channel = "commits" ), per_week( displayName = "Performance Experiment",
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Feb 23 01:54:48 GMT 2024 - 20.9K bytes - Viewed (0) -
.teamcity/src/main/kotlin/common/VersionedSettingsBranch.kt
/** * Whether the <a href="https://www.jetbrains.com/help/teamcity/configuring-vcs-triggers.html">VCS trigger</a> * should be enabled, i.e. when new commits are pushed to this branch, should a ReadyForNightly job * be triggered automatically? * * Currently, we only enable VCS trigger for `master`/`release`/`releaseNx` branches. */
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Tue Dec 05 00:08:14 GMT 2023 - 3.4K bytes - Viewed (0) -
.teamcity/README.md
- IMPORTANT NOTE: if the first import fails, you have to select and apply `Synchronization disabled`, then repeat the step above. Otherwise, TeamCity complains "Can't find the previous revision, please commit current settings first". - If anything bad happens, feel free to delete the project you created and retry (you may need to apply `Synchronization disabled` before deleting it).
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Wed Mar 06 23:02:25 GMT 2024 - 4K bytes - Viewed (0) -
build-logic-commons/basics/src/main/kotlin/gradlebuild/basics/BuildParams.kt
enum class FlakyTestStrategy { INCLUDE, EXCLUDE, ONLY } object BuildParams { const val BUILD_BRANCH = "BUILD_BRANCH" const val BUILD_COMMIT_ID = "BUILD_COMMIT_ID" const val BUILD_COMMIT_DISTRIBUTION = "buildCommitDistribution" const val BUILD_CONFIGURATION_ID = "BUILD_TYPE_ID" const val BUILD_FINAL_RELEASE = "finalRelease" const val BUILD_ID = "BUILD_ID"
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Mon Jan 01 01:23:31 GMT 2024 - 16.2K bytes - Viewed (0) -
.cm/lacks_tests.cm
# within the file. We keep each automation (or very closely related group of automations) in # its own file. on: - pr_created - commit - comment_added automations: # If a PR contains non-trivial source changes and no tests, add a comment to the PR lacks_tests: if: - {{ ('lacks_tests' | isEnabledAutomation(pr)) }}
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 2.4K bytes - Viewed (0) -
.cm/add_usual_expert.cm
# within the file. We keep each automation (or very closely related group of automations) in # its own file. on: - pr_created - commit - comment_added automations: # If someone is a primary author of the files in a change, but NOT the pr author, automatically add them as a reviewer. add_usual_expert: if:
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 1.4K bytes - Viewed (0) -
.cm/complex_changes.cm
# within the file. We keep each automation (or very closely related group of automations) in # its own file. on: - pr_created - commit - comment_added automations: # If a PR is very complex, require 2 approvals complex_changes: if: - {{ ('complex_changes' | isEnabledAutomation(pr)) }}
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 1.7K bytes - Viewed (0) -
CONTRIBUTING.md
### Creating commits and writing commit messages The commit messages that accompany your code changes are an important piece of documentation. Please follow these guidelines when creating commits: * [Write good commit messages.](https://cbea.ms/git-commit/#seven-rules)
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) -
build-logic-commons/module-identity/src/main/kotlin/gradlebuild/identity/tasks/BuildReceipt.kt
it.parentFile.mkdirs() } ReproduciblePropertiesWriter.store( Properties().apply { put("commitId", commitId.getOrElse("HEAD")) put("versionNumber", version.get()) put("baseVersion", baseVersion.get()) put("isSnapshot", snapshot.get().toString())
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Sat Sep 30 16:17:28 GMT 2023 - 4.2K bytes - Viewed (0)