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
Upgrading from Dependabot Preview to GitHub-native Dependabot requires only one step: merge the Upgrade to GitHub-native Dependabot pull request in your repository.
-In order to keep getting Dependabot updates, please merge this PR and migrate to GitHub-native Dependabot before then.+In order to keep getting Dependabot updates, please merge this PR.
being sufficient. Is that interpretation accurate?
The text was updated successfully, but these errors were encountered:
The majority of folks only need to merge the PR, then they're migrated. Folks who are using private repos/registries need to do a bit more work (grant Dependabot access to the repos/migrate their secrets), then they're migrated. I've clarified the docs (should be published shortly) and I'll work on clarifying the PR.
We just received the PR that updates the dependabot config to v2 (mui/material-ui#26024).
This PR mentions
If I need to "migrate to GitHub-native Dependabot before then" why not mention this first?
I then visited Learn more about migrating to GitHub-native Dependabot to find out how to "migrate to GitHub-native Dependabot".
Though this page says I only have to merge the PR:
-- https://docs.github.com/en/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot#upgrading-to-github-native-dependabot
I interpret this as
being sufficient. Is that interpretation accurate?
The text was updated successfully, but these errors were encountered: