在线时间:8:00-16:00
迪恩网络APP
随时随地掌握行业动态
扫描二维码
关注迪恩网络微信公众号
开源软件名称(OpenSource Name):dipien/releases-hub-gradle-plugin开源软件地址(OpenSource Url):https://github.com/dipien/releases-hub-gradle-plugin开源编程语言(OpenSource Language):Kotlin 96.3%开源软件介绍(OpenSource Introduction):Releases Hub Gradle PluginGradle Plugin to automatically upgrade your Java/Kotlin project dependencies and send a GitHub pull request with the changes. You can read this blog post for more detailed information. How it works
Features
SetupAdd the following configuration to your root Using the plugins DSL + Groovy: plugins {
id "com.dipien.releaseshub.gradle.plugin" version "X.Y.Z"
} Using the plugins DSL + Kotlin DSL: plugins {
id("com.dipien.releaseshub.gradle.plugin").version("X.Y.Z")
} Using legacy plugin application + Groovy: buildscript {
repositories {
mavenCentral()
}
dependencies {
classpath("com.dipien:releases-hub-gradle-plugin:X.Y.Z")
}
}
apply plugin: "com.dipien.releaseshub.gradle.plugin" Using legacy plugin application + Kotlin DSL: buildscript {
repositories {
mavenCentral()
}
dependencies {
classpath("com.dipien:releases-hub-gradle-plugin:X.Y.Z")
}
}
apply(plugin = "com.dipien.releaseshub.gradle.plugin") ConfigureHow to configure the propertiesAll the plugin configuration properties can be added using any of the following ways:
releasesHub {
gitHubRepository = "sample"
}
Common PropertiesAuto Detect Dependencies pathsWhether the plugin should automatically find the files where the dependencies are defined. This property is required. The default value is true
The plugin automatically find dependencies on the following files:
Dependencies pathsThe custom paths (relative to the project root directory) for the files where the dependencies are defined. This list is used in addition to the auto detected paths (if enabled). This property is optional. For example:
IncludesThe dependencies to include.
You can define a
ExcludesThe dependencies to exclude.
You can define a
If you need to exclude the Gradle upgrade, use "gradle". For example:
UsageVersion Catalog (libs.versions.toml file) exampleYou can define your dependencies on the gradle/libs.versions.toml
Root build.gradlebuildscript {
dependencies {
classpath(libs.kotlin.plugin)
}
}
dependencies {
implementation(libs.kotlin)
}
apply plugin: "kotlin"
apply plugin: "com.dipien.releaseshub.gradle.plugin" Version Catalog (settings.gradle.kts file) exampleYou can define your dependencies on the settings.gradle.kts
Root build.gradlebuildscript {
dependencies {
classpath(libs.kotlin.plugin)
}
}
dependencies {
implementation(libs.kotlin)
}
apply plugin: "kotlin"
apply plugin: "com.dipien.releaseshub.gradle.plugin" BuilsSrc exampleYou can define your dependencies on buildSrc/src/main/kotlin/Libs.ktobject Libs {
const val KOTLIN = "org.jetbrains.kotlin:kotlin-stdlib-jdk7:1.3.40"
} buildSrc/src/main/kotlin/BuildLibs.ktobject BuildLibs {
const val KOTLIN_PLUGIN = "org.jetbrains.kotlin:kotlin-gradle-plugin:1.3.41"
} Root build.gradlebuildscript {
dependencies {
classpath(BuildLibs.KOTLIN_PLUGIN)
}
}
dependencies {
implementation(Libs.KOTLIN)
}
apply plugin: "kotlin"
apply plugin: "com.dipien.releaseshub.gradle.plugin" See the sample for more details. To automate your dependencies upgrades, you can follow this guide: How to automate your dependencies upgrades with GitHub Actions TasksValidate dependenciesValidate all the dependencies. The following validations are executed:
PropertiesUnused ExcludesThe dependencies to exclude from the unused validation.
You can define a
Unused extensions to searchThe file extensions of the files where the artifact's packages will we search to find unused dependendencies.
By default
List dependenciesPrint all the dependencies that will be analyzed to upgrade.
List dependencies to upgradePrint all the dependencies that are upgradeable. A file
Upgrade dependenciesThis task creates a Github Pull Request for each groupId that have at least one dependency to upgrade. The following steps are executed for each
PropertiesPull Request EnabledWhether a pull request with all the upgrades should be created or not. The default value is
Pull Requests MaxThe maximum amount of pull requests to create during the task execution.
This is useful to avoid creating too much pull requests when you still have many dependencies to upgrade. The default value is
Pull Request LabelsThe list of labels to assign when creating the pull request. Optional list.
Pull Request AssigneeThe user to be assigned to the pull request. Optional string.
Pull Request ReviewersThe list of reviewers to assign when creating the pull request. Optional list.
Pull Request Team ReviewersThe list of team reviewers to assign when creating the pull request. Optional list.
Head Branch PrefixThe branch's prefix where the commit will be pushed. Also, the head branch's prefix of the pull request to create. Required String (only if
Base BranchThe pull request base branch. Optional String. The default value is
Git User NameThe Git user name used by the commit command. Optional String.
Git User EmailThe Git user email used by the commit command. Optional String.
GitHub RepositoryThe GitHub repository where the pull request will be created. Required String (only if
GitHub Repository OwnerThe GitHub repository owner where the pull request will be created. Required String (only if
GitHub Repository NameThe GitHub repository name where the pull request will be created. Required String (only if
GitHub Write TokenThe GitHub write token needed to access the GitHub API to create the pull request. Follow these steps to create your token.
We strongly recommend to not use the
GitHub Api Host NameThe GitHub api host name needed to access the GitHub Enterprise. Optional String.
VersioningThis project uses the Semantic Versioning guidelines for transparency into our release cycle. Privacy PolicyThe Sponsor this projectSponsor this open source project to help us get the funding we need to continue working on it.
You can donate BTC (lightning), using this QR: Follow us |
2023-10-27
2022-08-15
2022-08-17
2022-09-23
2022-08-13
请发表评论