Skip to content

Commit 0b52168

Browse files
kbukum1jc-clark
andauthored
Clarify that Dependabot workflows bypass Actions policy checks and disablement (github#38421)
Co-authored-by: Joe Clark <[email protected]>
1 parent b1d7355 commit 0b52168

File tree

2 files changed

+20
-1
lines changed

2 files changed

+20
-1
lines changed

content/code-security/dependabot/working-with-dependabot/about-dependabot-on-github-actions-runners.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: About Dependabot on GitHub Actions runners
3-
intro: '{% data variables.product.prodname_dotcom %} automatically runs the jobs that generate {% data variables.product.prodname_dependabot %} pull requests on {% data variables.product.prodname_actions %} if you have {% data variables.product.prodname_actions %} enabled for the repository.'
3+
intro: '{% data variables.product.prodname_dotcom %} automatically runs the jobs that generate {% data variables.product.prodname_dependabot %} pull requests on {% data variables.product.prodname_actions %} if you have {% data variables.product.prodname_actions %} enabled for the repository. When {% data variables.product.prodname_dependabot %} is enabled, these jobs will run by bypassing Actions policy checks and disablement at the repository or organization level.'
44
shortTitle: About Dependabot on Actions
55
product: '{% data reusables.gated-features.dependabot-on-actions %}'
66
versions:
@@ -17,6 +17,9 @@ topics:
1717

1818
## About {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_actions %} runners
1919

20+
> [!IMPORTANT]
21+
> If {% data variables.product.prodname_dependabot %} is enabled for a repository, it will always run on {% data variables.product.prodname_actions %}, **bypassing both Actions policy checks and disablement at the repository or organization level**. This ensures that security and version update workflows always run when Dependabot is enabled.
22+
2023
{% data reusables.dependabot.dependabot-updates-and-actions %}
2124

2225
{% data reusables.dependabot.dependabot-on-actions-future-note %}

content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,9 @@ You can use {% data variables.product.prodname_actions %} to perform automated t
3535

3636
## About {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_actions %}
3737

38+
> [!IMPORTANT]
39+
> If {% data variables.product.prodname_dependabot %} is enabled for a repository, it will always run on {% data variables.product.prodname_actions %}, **bypassing both Actions policy checks and disablement at the repository or organization level**. This ensures that security and version update workflows always run when Dependabot is enabled.
40+
3841
{% data variables.product.prodname_dependabot %} creates pull requests to keep your dependencies up to date. You can use {% data variables.product.prodname_actions %} to perform automated tasks when these pull requests are created. For example, fetch additional artifacts, add labels, run tests, or otherwise modify the pull request.
3942

4043
{% data reusables.dependabot.working-with-actions-considerations %} For more information, see [AUTOTITLE](/code-security/dependabot/troubleshooting-dependabot/troubleshooting-dependabot-on-github-actions).
@@ -187,6 +190,19 @@ jobs:
187190
> [!NOTE]
188191
> If you use status checks to test pull requests, you should enable **Require status checks to pass before merging** for the target branch for {% data variables.product.prodname_dependabot %} pull requests. This branch protection rule ensures that pull requests are not merged unless **all the required status checks pass**. For more information, see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule).
189192

193+
## {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_actions %} policies
194+
195+
Normally, whether a workflow can run in a repository depends on {% data variables.product.prodname_actions %} **policy checks** and whether {% data variables.product.prodname_actions %} is **enabled** at the organization or repository level. These controls can restrict workflows from running—especially when external actions are blocked or {% data variables.product.prodname_actions %} is disabled entirely.
196+
197+
However, when {% data variables.product.prodname_dependabot %} is enabled for a repository, its workflows will always run on {% data variables.product.prodname_actions %}, **bypassing both Actions policy checks and disablement**.
198+
199+
* {% data variables.product.prodname_dependabot %} workflows are not blocked by Actions disablement or enterprise policy restrictions.
200+
* The actions referenced within these workflows are also allowed to run, even if external actions are disallowed.
201+
202+
{% ifversion dependabot-on-actions-opt-in %}
203+
For more information, see [AUTOTITLE](/code-security/dependabot/working-with-dependabot/about-dependabot-on-github-actions-runners).
204+
{% endif %}
205+
190206
## Investigating failed workflow runs
191207

192208
If your workflow run fails, check the following:

0 commit comments

Comments
 (0)