You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
EDIT: This post is now outdated due to Dependabot being integrated into GitHub. Please check the linked pull-request to migrate to the new version of Dependabot.
I'm noticing that Dependabot does not seem to take the configuration file and apply it properly:
Dependabot is not applying the default label correctly, the config file says the label should be: dependabot. Instead it only applies the dependencies label.
Dependabot also didn't create the reviewer ben correctly.
I would expect you to see something similar to the dependabot configuration screenshot (on the dashboard click on the gear/cog next to the repository name):
See #1355 for the Dependabot pull-request that's not working right.
The text was updated successfully, but these errors were encountered:
EDIT: I've made a pull-request to help you migrate. 😄 You can see it linked below.
HonkingGoose
changed the title
Dependabot configuration file doesn't seem to be read by Dependabot
Migrate from Dependabot preview to Dependabot
Jun 5, 2020
EDIT: This post is now outdated due to Dependabot being integrated into GitHub. Please check the linked pull-request to migrate to the new version of Dependabot.
I'm noticing that Dependabot does not seem to take the configuration file and apply it properly:
dependabot
. Instead it only applies thedependencies
label.ben
correctly.I've validated the current config file at https://dependabot.com/docs/config-file/validator/ and that says that everything is fine.
I think you should check the Dependabot dashboard, to see what that says:

https://app.dependabot.com
I would expect you to see something similar to the dependabot configuration screenshot (on the dashboard click on the gear/cog next to the repository name):
See #1355 for the Dependabot pull-request that's not working right.
The text was updated successfully, but these errors were encountered: