feat(recipes): Add a dependabot GitHub action file #338
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #337.
Thanks a lot for the tip, @jonesbusy, I didn't know we could do as simple as that. 😉
Summary
New Features
Walkthrough
The changes in this pull request introduce a new recipe for Jenkins plugin dependency management, specifically
io.jenkins.tools.pluginmodernizer.AddDependencyCheck
, which facilitates the integration of a GitHub action for dependency checking.Changes
plugin-modernizer-core/src/main/resources/META-INF/rewrite/recipes.yml
AddDependencyCheck
for GitHub action dependency checking.Testing done
rm -fr ~/.cache/jenkins-plugin-modernizer-cli/vagrant/ && java -jar plugin-modernizer-cli/target/jenkins-plugin-modernizer-999999-SNAPSHOT.jar --plugins vagrant --recipes MinimalBuildJava8,AddOrModernizeJenkinsFile,AddDependencyCheck --debug
produced the following PR: jenkinsci/vagrant-plugin#13.Submitter checklist
Link to relevant pull requests, esp. upstream and downstream changes