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: github/create-pull-request/docs/concepts-guidelines.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,15 +88,15 @@ In these cases, you *must supply* the `base` input so the action can rebase chan
88
88
Workflows triggered by [`pull_request`](https://docs.github.com/en/actions/reference/events-that-trigger-workflows#pull_request) events will by default check out a merge commit. Set the `base` input as follows to base the new pull request on the current pull request's branch.
89
89
90
90
```yml
91
-
- uses: peter-evans/create-pull-request@v4
91
+
- uses: peter-evans/create-pull-request@v6
92
92
with:
93
93
base: ${{ github.head_ref }}
94
94
```
95
95
96
96
Workflows triggered by [`release`](https://docs.github.com/en/actions/reference/events-that-trigger-workflows#release) events will by default check out a tag. For most use cases, you will need to set the `base` input to the branch name of the tagged commit.
97
97
98
98
```yml
99
-
- uses: peter-evans/create-pull-request@v4
99
+
- uses: peter-evans/create-pull-request@v6
100
100
with:
101
101
base: main
102
102
```
@@ -180,7 +180,7 @@ Checking out a branch from a different repository from where the workflow is exe
180
180
181
181
# Make changes to pull request here
182
182
183
-
- uses: peter-evans/create-pull-request@v4
183
+
- uses: peter-evans/create-pull-request@v6
184
184
with:
185
185
token: ${{ secrets.PAT }}
186
186
```
@@ -207,7 +207,7 @@ How to use SSH (deploy keys) with create-pull-request action:
207
207
# Make changes to pull request here
208
208
209
209
- name: Create Pull Request
210
-
uses: peter-evans/create-pull-request@v4
210
+
uses: peter-evans/create-pull-request@v6
211
211
```
212
212
213
213
### Push pull request branches to a fork
@@ -230,7 +230,7 @@ Note that if you choose to use this method (not give the machine account `write`
230
230
231
231
# Make changes to pull request here
232
232
233
-
- uses: peter-evans/create-pull-request@v4
233
+
- uses: peter-evans/create-pull-request@v6
234
234
with:
235
235
token: ${{ secrets.MACHINE_USER_PAT }}
236
236
push-to-fork: machine-user/fork-of-repository
@@ -273,7 +273,7 @@ GitHub App generated tokens are more secure than using a PAT because GitHub App
273
273
# Make changes to pull request here
274
274
275
275
- name: Create Pull Request
276
-
uses: peter-evans/create-pull-request@v4
276
+
uses: peter-evans/create-pull-request@v6
277
277
with:
278
278
token: ${{ steps.generate-token.outputs.token }}
279
279
```
@@ -314,7 +314,7 @@ The action can use GPG to sign commits with a GPG key that you generate yourself
0 commit comments