Forks don't get the settings for the Dependabot features when you fork them (makes some sense since they often need issues, which are not enabled on a fork to help getting the issues back to the parent repo). Even enabling the setting on the organization that all new repos have Dependabot enabled, will not enable Dependabot on new forks (you can update the rights from the org level after the fact).
[ ] After creating the fork, call the API to enable the Dependabot features (the top two, the third one will generate PR's which we don't need)
rajbos
commented
2 years ago
Forks don't get the settings for the Dependabot features when you fork them (makes some sense since they often need issues, which are not enabled on a fork to help getting the issues back to the parent repo). Even enabling the setting on the organization that all new repos have Dependabot enabled, will not enable Dependabot on new forks (you can update the rights from the org level after the fact).