From 5a074817fb3bb2a704d2a24581f103eb18533d8a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Heath=20Dutton=F0=9F=95=B4=EF=B8=8F?=
 <heathdutton@gmail.com>
Date: Wed, 14 Jan 2026 19:46:07 -0500
Subject: [PATCH] Fix reusable template expansion in Dependabot Actions
 examples

---
 .../automating-dependabot-with-github-actions.md | 16 ----------------
 1 file changed, 16 deletions(-)

diff --git a/content/code-security/tutorials/secure-your-dependencies/automating-dependabot-with-github-actions.md b/content/code-security/tutorials/secure-your-dependencies/automating-dependabot-with-github-actions.md
index d6de57f93ce1..29678802f8a9 100644
--- a/content/code-security/tutorials/secure-your-dependencies/automating-dependabot-with-github-actions.md
+++ b/content/code-security/tutorials/secure-your-dependencies/automating-dependabot-with-github-actions.md
@@ -51,8 +51,6 @@ Most automation requires you to know information about the contents of the pull
 
 Example:
 
-{% raw %}
-
 ```yaml copy
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 name: Dependabot fetch metadata
@@ -78,8 +76,6 @@ jobs:
       #  - steps.metadata.outputs.update-type
 ```
 
-{% endraw %}
-
 For more information, see the [`dependabot/fetch-metadata`](https://github.com/dependabot/fetch-metadata) repository.
 
 ## Labeling a pull request
@@ -88,8 +84,6 @@ If you have other automation or triage workflows based on {% data variables.prod
 
 Example that flags all production dependency updates with a label:
 
-{% raw %}
-
 ```yaml copy
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 name: Dependabot auto-label
@@ -116,16 +110,12 @@ jobs:
           PR_URL: ${{github.event.pull_request.html_url}}
 ```
 
-{% endraw %}
-
 ## Automatically approving a pull request
 
 You can automatically approve {% data variables.product.prodname_dependabot %} pull requests by using the {% data variables.product.prodname_cli %} in a workflow.
 
 Example:
 
-{% raw %}
-
 ```yaml copy
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 name: Dependabot auto-approve
@@ -151,8 +141,6 @@ jobs:
           GH_TOKEN: ${{secrets.GITHUB_TOKEN}}
 ```
 
-{% endraw %}
-
 ## Enabling automerge on a pull request
 
 If you want to allow maintainers to mark certain pull requests for automerge, you can use {% data variables.product.prodname_dotcom %}'s automerge functionality. This enables the pull request to be merged when any tests and approvals required by the branch protection rules are successfully met.
@@ -161,8 +149,6 @@ For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-req
 
 You can instead use {% data variables.product.prodname_actions %} and the {% data variables.product.prodname_cli %}. Here is an example that automerges all patch updates to `my-dependency`:
 
-{% raw %}
-
 ```yaml copy
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 name: Dependabot auto-merge
@@ -190,8 +176,6 @@ jobs:
           GH_TOKEN: ${{secrets.GITHUB_TOKEN}}
 ```
 
-{% endraw %}
-
 > [!NOTE]
 > 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).