-
Notifications
You must be signed in to change notification settings - Fork 795
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ci] fix dependabot config and expand to Cargo and GitHub Actions #25791
base: master
Are you sure you want to change the base?
Conversation
The additional `reviewers` field is preventing dependabot from running. Signed-off-by: Gary Guo <[email protected]>
Signed-off-by: Gary Guo <[email protected]>
Signed-off-by: Gary Guo <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks. Is there a way to do a test run?
Also, I double checked and dependabot doesn't support Bazel yet (though renovate does).
I'm not aware of a way to trigger a manual run |
I enabled dependabot updates on my fork and it starts creating PRs: https://github.com/nbdd0121/opentitan/pulls?q=sort%3Aupdated-desc+is%3Apr+is%3Aopen |
In https://github.com/nbdd0121/opentitan/network/updates/944443966, somehow it's trying to evaluate yum-requirements.txt as Python requirements file? Also, we probably want to ensure Cargo dependencies are up-to-date before merging this PR to avoid a lot of dependabot PRs. |
Do we want it to be creating PRs? I think the security advisories tab would be good enough |
My fork's security advisory page doesn't include third_party/rust/Cargo.toml as a source. Maybe I'll need to wait a bit for GitHub to rescan. |
The additional
reviewers
field is preventing dependabot from running. Fix it, and also expand the scanned dependencies to Rust crates and GitHub Actions.