-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
fix dependabot config #15668
fix dependabot config #15668
Conversation
/assign @skonto |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #15668 +/- ##
==========================================
+ Coverage 83.51% 83.55% +0.04%
==========================================
Files 219 219
Lines 17427 17427
==========================================
+ Hits 14554 14562 +8
+ Misses 2502 2494 -8
Partials 371 371 ☔ View full report in Codecov by Sentry. |
/retest |
patterns: | ||
- "*" | ||
patterns: | ||
- "*" |
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.
nit: Although both are accepted by yaml, probably adding space for array items is mor ereadable, also as in the example here.
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dprotaso, skonto The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/override ? |
@skonto: skonto unauthorized: /override is restricted to Repo administrators. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@dprotaso could you override the failing test (I have no rights) or do you know why it didnt keep the artifact around? |
It's a 'best' effort cache. We need to re-kick off the build step first |
lol we hit a weird prow bug |
Fixing the config after merging - #15475