Clarify that Dependabot workflows bypass Actions policy checks and disablement

[kbukum1]

Why:

Closes: https://github.com/github/docs-content/issues/14456

What's being changed (if available, include any code snippets, screenshots, or gifs):

This PR updates the documentation to clarify the behavior of Dependabot when GitHub Actions is disabled or restricted by policy checks.

Pages updated:

• automating-dependabot-with-github-actions.md
• about-dependabot-on-github-actions-runners.md

Key changes:

• Clearly document that Dependabot workflows will always run when enabled, regardless of whether:
  • GitHub Actions is disabled at the repository or organization level
  • Enterprise or org-level policy checks block external actions
• Added a [!IMPORTANT] note to both pages emphasizing this behavior
• Rewrote the "📌 Dependabot and GitHub Actions Policies" section to first explain normal GitHub Actions enforcement, then describe Dependabot's exception
• Updated intro: metadata in the second doc to reflect the bypass behavior

These updates ensure that customers understand why Dependabot workflows run even when other GitHub Actions workflows may be restricted or blocked.

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing and the changes look good in the review environment.

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
code-security/dependabot/working-with-dependabot/about-dependabot-on-github-actions-runners.md	fpt ghec	fpt ghec
code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md	fpt ghec ghes@ 3.17 3.16 3.15 3.14 3.13	fpt ghec ghes@ 3.17 3.16 3.15 3.14 3.13

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[docs-bot]

Previous broken links comment now moot. 👌😙

[Copilot]

Pull Request Overview

This PR clarifies that enabling Dependabot workflows bypasses GitHub Actions policy checks and disablement, ensuring users understand that these workflows always run regardless of repository or enterprise settings.

• Adds an IMPORTANT callout to the "Automating Dependabot with GitHub Actions" page.
• Introduces a new "📌 Dependabot and GitHub Actions Policies" section explaining policy and disablement bypass.
• Updates the intro and adds an IMPORTANT callout in the "About Dependabot on GitHub Actions runners" page.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md	Added an IMPORTANT note and a new policy section detailing how Dependabot bypasses Actions policies and disablement.
content/code-security/dependabot/working-with-dependabot/about-dependabot-on-github-actions-runners.md	Updated the intro to mention bypass behavior and added an IMPORTANT callout in the "About" section.

[jc-clark]

Looks good from docs content! I'll commit a couple small updates and then go ahead and merge. Thanks @kbukum1!

[github-actions]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡