Skip to content

Commit 5a07481

Browse files
committed
Fix reusable template expansion in Dependabot Actions examples
1 parent 4f4f2f7 commit 5a07481

File tree

1 file changed

+0
-16
lines changed

1 file changed

+0
-16
lines changed

content/code-security/tutorials/secure-your-dependencies/automating-dependabot-with-github-actions.md

Lines changed: 0 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -51,8 +51,6 @@ Most automation requires you to know information about the contents of the pull
5151

5252
Example:
5353

54-
{% raw %}
55-
5654
```yaml copy
5755
{% data reusables.actions.actions-not-certified-by-github-comment %}
5856
name: Dependabot fetch metadata
@@ -78,8 +76,6 @@ jobs:
7876
# - steps.metadata.outputs.update-type
7977
```
8078

81-
{% endraw %}
82-
8379
For more information, see the [`dependabot/fetch-metadata`](https://github.com/dependabot/fetch-metadata) repository.
8480

8581
## Labeling a pull request
@@ -88,8 +84,6 @@ If you have other automation or triage workflows based on {% data variables.prod
8884

8985
Example that flags all production dependency updates with a label:
9086

91-
{% raw %}
92-
9387
```yaml copy
9488
{% data reusables.actions.actions-not-certified-by-github-comment %}
9589
name: Dependabot auto-label
@@ -116,16 +110,12 @@ jobs:
116110
PR_URL: ${{github.event.pull_request.html_url}}
117111
```
118112
119-
{% endraw %}
120-
121113
## Automatically approving a pull request
122114
123115
You can automatically approve {% data variables.product.prodname_dependabot %} pull requests by using the {% data variables.product.prodname_cli %} in a workflow.
124116
125117
Example:
126118
127-
{% raw %}
128-
129119
```yaml copy
130120
{% data reusables.actions.actions-not-certified-by-github-comment %}
131121
name: Dependabot auto-approve
@@ -151,8 +141,6 @@ jobs:
151141
GH_TOKEN: ${{secrets.GITHUB_TOKEN}}
152142
```
153143
154-
{% endraw %}
155-
156144
## Enabling automerge on a pull request
157145
158146
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
161149
162150
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`:
163151

164-
{% raw %}
165-
166152
```yaml copy
167153
{% data reusables.actions.actions-not-certified-by-github-comment %}
168154
name: Dependabot auto-merge
@@ -190,8 +176,6 @@ jobs:
190176
GH_TOKEN: ${{secrets.GITHUB_TOKEN}}
191177
```
192178

193-
{% endraw %}
194-
195179
> [!NOTE]
196180
> 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).
197181

0 commit comments

Comments
 (0)