-
Notifications
You must be signed in to change notification settings - Fork 41
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
Add dependabot #1051
Add dependabot #1051
Conversation
98eb771
to
1b4c6fc
Compare
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.
Seems like a good idea.
My only thought around this is that we shouldn't update before k6 unless there's a good reason to do so (blocking us due to a bug in a dependency etc).
Thanks, @ankur22 😊
No worries. The bot only makes PRs, and we can decide whether to merge them. It has a UI that we can talk to using Github comments. So, we can include or exclude some of the dependencies per PR. |
6fe33b0
to
800a8e6
Compare
@ankur22 I made some changes because the configuration syntax was incorrect. |
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.
LGTM 🚀
This will keep our dependencies up-to-date.
Co-authored-by: Ankur Agarwal <ankur.agarwal@grafana.com>
8e28d45
to
2a4636a
Compare
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.
LGTM 🚀
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.
LGTM 👏
What?
Adds Github dependabot for our repository.
Why?
To keep our dependencies up to date, like k6-core, CDP proto, etc.
We usually do this manually, which can be a hassle and causes our dependencies go stale:
Checklist