Incorrect steps to enable dependabot version updates on forked repository

Question

In module "Configure Dependabot security updates on your GitHub repo", unit "Dependabot security updates", section "Version updates on forks" it says:

"To enable version updates on the fork of a repository:

1. Go to the main page of the repository where you want to enable version updates.
2. Select Insights.
3. Select Dependency graph from the left sidebar.
4. Select Dependabot.
5. Select Create config file.
6. Edit dependabot.yml config file
7. Commit and merge dependabot.yml file"

Those steps are incorrect because the forked repo already contains that file. The only extra step is to enable "Dependabot version updates". See official GitHub Docs: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#enabling-version-updates-on-forks

This question is related to the following Learning Module

Answer 1

Hi Carlos Quintero,

We want to assure you that our team is fully aware of the issue and is actively working towards a solution. We understand that this might be causing some inconvenience, and we’re committed to resolving it as quickly as possible.

In the meantime, we recommend that you continue progressing through the Learning Paths, but without completing the exercise modules for now. These exercises are temporarily unavailable, but the rest of the Learning Path content should still help you move forward in your learning.

Once we have a fix or further information, we’ll update you right away.

We greatly appreciate your patience and understanding during this time, and we’re working hard to provide a smooth learning experience for you.