jprdonnelly/docs
1
0
Fork 0
mirror of synced 2026-01-01 09:04:46 -05:00
Code Issues Projects Releases Wiki Activity

Merge pull request #17773 from burnettk/patch-2

Browse Source 
clarify that there are two different auto-merge approaches
This commit is contained in:
mc
2022-05-13 14:42:31 +01:00
committed by GitHub
parent c9b833d6b6 0d8b875032
commit 3b7de42a9a
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -452,9 +452,9 @@ jobs:
### Enable auto-merge on a pull request
If you want to auto-merge your pull requests, you can use {% data variables.product.prodname_dotcom %}'s auto-merge functionality. This enables the pull request to be merged when all required tests and approvals are successfully met. For more information on auto-merge, see "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)."
If you want to allow maintainers to mark certain pull requests for auto-merge, you can use {% data variables.product.prodname_dotcom %}'s auto-merge functionality. This enables the pull request to be merged when all required tests and approvals are successfully met. For more information on auto-merge, see "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)."
Here is an example of enabling auto-merge for all patch updates to `my-dependency`:
You can instead use {% data variables.product.prodname_actions %} and the {% data variables.product.prodname_cli %}. Here is an example that auto merges all patch updates to `my-dependency`:
{% ifversion ghes = 3.3 %}