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: Add dependabot #536
ci: Add dependabot #536
Conversation
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.
Thanks for suggesting this. Looks pretty straightforward to me!
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.
Ah, one second. I'd probably move this alongside the other CI workflows into the .github/workflows/
directory. Other than that, this is good to go.
I suppose it's not possible because it must be stored exactly in the
|
Are you sure that subdirectories won't work? Should we try? |
I'm not sure, let's try |
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 like everyone puts in .github
and not the workflows subdirectory.
But it does seem to work in sub-directories as well. @SKY-ALIN was so gracious as to try it out in the |
Would you nevertheless argue to keep it in the main |
Let's check how it works in the rust-bio-types repo. If we don't receive new PRs from Dependabot in a week, just move it back |
Yes, let's do that. And feel free to ping me in again, once you check! |
I lean towards convention, but no strong preference myself. Waiting on the other repo and if it works, leaving it in the subdirectory sounds like a plan. |
Finally, it doesn't work like that. We have to move it back to |
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.
Thanks for following up on this
Dismissing in order to merge given we've arrived at our answer of where the file needs to be
Also, I realized we need to add a conventional commit prefix to the commit messages, to make the respective check pass. The suggested fix is in PR #542 (for future reference, if any of us introduce the |
Dependabot will make PRs to update dependencies weekly, it helps keep dependencies up to date. You don't need to add something to the repository's settings or this PR, it'll start to work after the merge.
GitHub page about it
An article about it on Medium