-
Notifications
You must be signed in to change notification settings - Fork 64.6k
Description
Code of Conduct
- I have read and agree to the GitHub Docs project's Code of Conduct
What article on docs.github.com is affected?
What part(s) of the article would you like to see updated?
I think that the following sentences contradict each other
If Dependabot is enabled for a repository, it will always run on GitHub Actions, bypassing both Actions policy checks and disablement at the repository or organization level.
If you enable Dependabot on a new repository and have GitHub Actions disabled, Dependabot will run on the legacy application in GitHub to perform Dependabot updates
From my testing, even if Actions are disabled, Dependabot will still run using GitHub Actions. This "legacy application" the docs refer to may no longer exist or may only be triggered for very specific scenarios that are not clear.
With that, the note below may also be outdated as this is what seems to be the only behavior
Future releases of GitHub will always run Dependabot using GitHub Actions, and you will no longer have the option to enable or disable this setting.
Additional information
I executed dependabot from a repository with Actions disabled but the job execution was still using GitHub Actions:
See https://github.com/yeikel/log-captor/actions/runs/19252685897/job/55040666747
I also tried the following workflow:
- Create a repository
- Disable Actions
- Enable Dependabot
Even with that workflow, Dependabot still ran using GitHub Actions.