Add dependabot to monitor GHA#1567
Merged
dbwiddis merged 2 commits intojava-native-access:masterfrom Nov 24, 2023
Merged
Conversation
Signed-off-by: Pedro Kaj Kjellerup Nacht <[email protected]>
Signed-off-by: Pedro Kaj Kjellerup Nacht <[email protected]>
dbwiddis
approved these changes
Nov 24, 2023
Contributor
dbwiddis
left a comment
dbwiddis
left a comment
There was a problem hiding this comment.
No objection here, although personally I prefer Mend Renovate.
Contributor
Author
|
Ah yeah, Renovate works just as well! I just can't set it up, has to be a maintainer. But if you'd rather use that, feel free! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 #1566.
This PR adds Dependabot to monitor JNA's GitHub Actions. It also bumps
actions/checkout@v3tov4, the sort of thing Dependabot would otherwise do itself (see the PR on my fork).Dependabot is configured to use grouped updates. So if more than one Action releases a new version, you'll only receive a single PR updating all Actions instead of one PR per Action. This admittedly isn't too likely to happen currently, seeing as the project only uses two Actions, but can prove far more useful should the project add more workflows with more Actions in the future.