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/common-issues.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ So the straightforward solution is to just not install them during the workflow
37
37
38
38
- If hooks are automatically enabled by a framework, use an option provided by the framework to disable them. For example, for Husky users, they can be disabled with the `--ignore-scripts` flag, or by setting the `HUSKY` environment variable when the action runs.
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
@@ -92,15 +92,15 @@ In these cases, you *must supply* the `base` input so the action can rebase chan
92
92
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.
93
93
94
94
```yml
95
-
- uses: peter-evans/create-pull-request@v7
95
+
- uses: peter-evans/create-pull-request@v8
96
96
with:
97
97
base: ${{ github.head_ref }}
98
98
```
99
99
100
100
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.
101
101
102
102
```yml
103
-
- uses: peter-evans/create-pull-request@v7
103
+
- uses: peter-evans/create-pull-request@v8
104
104
with:
105
105
base: main
106
106
```
@@ -186,7 +186,7 @@ Checking out a branch from a different repository from where the workflow is exe
186
186
187
187
# Make changes to pull request here
188
188
189
-
- uses: peter-evans/create-pull-request@v7
189
+
- uses: peter-evans/create-pull-request@v8
190
190
with:
191
191
token: ${{ secrets.PAT }}
192
192
```
@@ -217,7 +217,7 @@ How to use SSH (deploy keys) with create-pull-request action:
217
217
# Make changes to pull request here
218
218
219
219
- name: Create Pull Request
220
-
uses: peter-evans/create-pull-request@v7
220
+
uses: peter-evans/create-pull-request@v8
221
221
```
222
222
223
223
### Push pull request branches to a fork
@@ -242,7 +242,7 @@ It will use their own fork to push code and create the pull request.
242
242
243
243
# Make changes to pull request here
244
244
245
-
- uses: peter-evans/create-pull-request@v7
245
+
- uses: peter-evans/create-pull-request@v8
246
246
with:
247
247
token: ${{ secrets.MACHINE_USER_PAT }}
248
248
push-to-fork: machine-user/fork-of-repository
@@ -285,7 +285,7 @@ The following is an example of pushing to a fork using GitHub App tokens.
0 commit comments