You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/concepts-guidelines.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ For each [event type](https://docs.github.com/en/actions/reference/events-that-t
40
40
The default can be overridden by specifying a `ref` on checkout.
41
41
42
42
```yml
43
-
- uses: actions/checkout@v4
43
+
- uses: actions/checkout@v6
44
44
with:
45
45
ref: develop
46
46
```
@@ -77,7 +77,7 @@ jobs:
77
77
example:
78
78
runs-on: ubuntu-latest
79
79
steps:
80
-
- uses: actions/checkout@v4
80
+
- uses: actions/checkout@v6
81
81
```
82
82
83
83
There may be use cases where it makes sense to execute the workflow on a branch that is not the base of the pull request. In these cases, the base branch can be specified with the `base` action input. The action will attempt to rebase changes made during the workflow on to the actual base.
@@ -179,7 +179,7 @@ This action uses [ncc](https://github.com/vercel/ncc) to compile the Node.js cod
179
179
Checking out a branch from a different repository from where the workflow is executing will make *that repository* the target for the created pull request. In this case, the `GITHUB_TOKEN` will not work and one of the other [token options](../README.md#token) must be used.
180
180
181
181
```yml
182
-
- uses: actions/checkout@v4
182
+
- uses: actions/checkout@v6
183
183
with:
184
184
token: ${{ secrets.PAT }}
185
185
repository: owner/repo
@@ -210,7 +210,7 @@ How to use SSH (deploy keys) with create-pull-request action:
210
210
211
211
```yml
212
212
steps:
213
-
- uses: actions/checkout@v4
213
+
- uses: actions/checkout@v6
214
214
with:
215
215
ssh-key: ${{ secrets.SSH_PRIVATE_KEY }}
216
216
@@ -238,7 +238,7 @@ It will use their own fork to push code and create the pull request.
238
238
6. As shown in the following example workflow, set the `push-to-fork` input to the full repository name of the fork.
239
239
240
240
```yaml
241
-
- uses: actions/checkout@v4
241
+
- uses: actions/checkout@v6
242
242
243
243
# Make changes to pull request here
244
244
@@ -280,7 +280,7 @@ The following is an example of pushing to a fork using GitHub App tokens.
280
280
owner: owner
281
281
repositories: fork-of-repo
282
282
283
-
- uses: actions/checkout@v4
283
+
- uses: actions/checkout@v6
284
284
285
285
# Make changes to pull request here
286
286
@@ -325,7 +325,7 @@ GitHub App generated tokens can be configured with fine-grained permissions and
325
325
app-id: ${{ secrets.APP_ID }}
326
326
private-key: ${{ secrets.APP_PRIVATE_KEY }}
327
327
328
-
- uses: actions/checkout@v4
328
+
- uses: actions/checkout@v6
329
329
330
330
# Make changes to pull request here
331
331
@@ -350,7 +350,7 @@ In the following example, a pull request is being created in remote repo `owner/
350
350
owner: owner
351
351
repositories: repo
352
352
353
-
- uses: actions/checkout@v4
353
+
- uses: actions/checkout@v6
354
354
with:
355
355
token: ${{ steps.generate-token.outputs.token }} # necessary if the repo is private
356
356
repository: owner/repo
@@ -382,7 +382,7 @@ The action can sign commits as `github-actions[bot]` when using the repository's
382
382
In this example the `token` input is not supplied, so the action will use the repository's default `GITHUB_TOKEN`. This will sign commits as `github-actions[bot]`.
383
383
```yaml
384
384
steps:
385
-
- uses: actions/checkout@v4
385
+
- uses: actions/checkout@v6
386
386
387
387
# Make changes to pull request here
388
388
@@ -395,7 +395,7 @@ In this example the `token` input is not supplied, so the action will use the re
395
395
In this example, the `token` input is generated using a GitHub App. This will sign commits as `<application-name>[bot]`.
396
396
```yaml
397
397
steps:
398
-
- uses: actions/checkout@v4
398
+
- uses: actions/checkout@v6
399
399
400
400
- uses: actions/create-github-app-token@v2
401
401
id: generate-token
@@ -437,7 +437,7 @@ The action can use GPG to sign commits with a GPG key that you generate yourself
0 commit comments