Skip to content

Commit a379af6

Browse files
v1.8
1 parent 743f69d commit a379af6

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

README.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ jobs:
2323
clubhouse:
2424
runs-on: ubuntu-latest
2525
steps:
26-
- uses: singingwolfboy/create-linked-clubhouse-story@v1.7
26+
- uses: singingwolfboy/create-linked-clubhouse-story@v1.8
2727
with:
2828
github-token: ${{ secrets.GITHUB_TOKEN }}
2929
clubhouse-token: ${{ secrets.CLUBHOUSE_TOKEN }}
@@ -59,7 +59,7 @@ You can customize the comment posted on pull requests using the `comment-templat
5959
variable, like this:
6060

6161
```yaml
62-
- uses: singingwolfboy/create-linked-clubhouse-story@v1.7
62+
- uses: singingwolfboy/create-linked-clubhouse-story@v1.8
6363
with:
6464
github-token: ${{ secrets.GITHUB_TOKEN }}
6565
clubhouse-token: ${{ secrets.CLUBHOUSE_TOKEN }}
@@ -89,7 +89,7 @@ You can customize the Clubhouse **title** and **description** when creating stor
8989
variables, like this:
9090

9191
```yaml
92-
- uses: singingwolfboy/create-linked-clubhouse-story@v1.7
92+
- uses: singingwolfboy/create-linked-clubhouse-story@v1.8
9393
with:
9494
github-token: ${{ secrets.GITHUB_TOKEN }}
9595
clubhouse-token: ${{ secrets.CLUBHOUSE_TOKEN }}
@@ -127,7 +127,7 @@ map GitHub users to Clubhouse users. The user map should be passed in the
127127
formatted string. Here's an example:
128128

129129
```yaml
130-
- uses: singingwolfboy/create-linked-clubhouse-story@v1.7
130+
- uses: singingwolfboy/create-linked-clubhouse-story@v1.8
131131
with:
132132
github-token: ${{ secrets.GITHUB_TOKEN }}
133133
clubhouse-token: ${{ secrets.CLUBHOUSE_TOKEN }}
@@ -155,7 +155,7 @@ You can also add a list of GitHub users to ignore for this integration by using
155155
Multiple users should be separated by commas.
156156

157157
```yaml
158-
- uses: singingwolfboy/create-linked-clubhouse-story@v1.7
158+
- uses: singingwolfboy/create-linked-clubhouse-story@v1.8
159159
with:
160160
github-token: ${{ secrets.GITHUB_TOKEN }}
161161
clubhouse-token: ${{ secrets.CLUBHOUSE_TOKEN }}
@@ -169,7 +169,7 @@ You can also add a list of GitHub `only-users` for this integration. This works
169169
Multiple users should be separated by commas.
170170

171171
```yaml
172-
- uses: singingwolfboy/create-linked-clubhouse-story@v1.7
172+
- uses: singingwolfboy/create-linked-clubhouse-story@v1.8
173173
with:
174174
github-token: ${{ secrets.GITHUB_TOKEN }}
175175
clubhouse-token: ${{ secrets.CLUBHOUSE_TOKEN }}
@@ -218,7 +218,7 @@ Next, provide a JSON-formatted string to the `label-iteration-group-map` input.
218218
This is used to map GitHub labels to Clubhouse groups. Here is an example:
219219

220220
```yaml
221-
- uses: singingwolfboy/create-linked-clubhouse-story@v1.7
221+
- uses: singingwolfboy/create-linked-clubhouse-story@v1.8
222222
with:
223223
github-token: ${{ secrets.GITHUB_TOKEN }}
224224
clubhouse-token: ${{ secrets.CLUBHOUSE_TOKEN }}

0 commit comments

Comments
 (0)