Skip to content

Fix reusable template expansion in Dependabot Actions examples #42195

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
heathdutton wants to merge 1 commit into
base: main
Choose a base branch
from
+0 −16
Open

Fix reusable template expansion in Dependabot Actions examples #42195

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 0 additions & 16 deletions ...dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,8 +50,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
Expand All @@ -77,8 +75,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
Expand All @@ -87,8 +83,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
Expand All @@ -115,16 +109,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
Expand All @@ -150,8 +140,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.
Expand All @@ -160,8 +148,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
Expand Down Expand Up @@ -189,8 +175,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).

Expand Down
Loading