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: README.md
+1-11Lines changed: 1 addition & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -73,17 +73,6 @@ Note that in order to read the step output the action step must have an id.
73
73
echo "Pull Request Number - ${{ steps.cpr.outputs.pull-request-number }}"
74
74
```
75
75
76
-
### Checkout
77
-
78
-
This action expects repositories to be checked out with `actions/checkout@v2`.
79
-
80
-
If there is some reason you need to use `actions/checkout@v1` the following step can be added to checkout the branch.
81
-
82
-
```yml
83
-
- uses: actions/checkout@v1
84
-
- run: git checkout "${GITHUB_REF:11}"
85
-
```
86
-
87
76
### Action behaviour
88
77
89
78
The default behaviour of the action is to create a pull request that will be continually updated with new changes until it is merged or closed.
@@ -115,6 +104,7 @@ To use this strategy, set input `branch-suffix` with one of the following option
115
104
### Controlling commits
116
105
117
106
As well as relying on the action to handle uncommitted changes, you can additionally make your own commits before the action runs.
107
+
Note that the repository must be checked out on a branch with a remote, it won't work for [events which checkout a commit](docs/concepts-guidelines.md#events-which-checkout-a-commit).
0 commit comments