Skip to content

Commit 7e7c19c

Browse files
v1.6
1 parent 5130a7f commit 7e7c19c

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

README.md

Lines changed: 10 additions & 10 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.5
26+
- uses: singingwolfboy/create-linked-clubhouse-story@v1.6
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.5
62+
- uses: singingwolfboy/create-linked-clubhouse-story@v1.6
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.5
92+
- uses: singingwolfboy/create-linked-clubhouse-story@v1.6
9393
with:
9494
github-token: ${{ secrets.GITHUB_TOKEN }}
9595
clubhouse-token: ${{ secrets.CLUBHOUSE_TOKEN }}
@@ -98,10 +98,10 @@ variables, like this:
9898
merged-state-name: Done
9999
closed-state-name: Abandoned
100100
story-title-template: >-
101-
{{{ payload.repository.name }}} - {{{ payload.pull_request.title }}}
101+
{{{ payload.repository.name }}} - {{{ payload.pull_request.title }}}
102102
story-description-template: >-
103-
:zap: New story created for pull request [**{{{ payload.pull_request.title }}}**]({{{ payload.pull_request.html_url }}})
104-
in repo **{{{ payload.repository.name }}}**.
103+
:zap: New story created for pull request [**{{{ payload.pull_request.title }}}**]({{{ payload.pull_request.html_url }}})
104+
in repo **{{{ payload.repository.name }}}**.
105105
{{{ #payload.pull_request.body }}}
106106
The body of the PR is: {{{ payload.pull_request.body }}}
107107
{{{ /payload.pull_request.body }}}
@@ -110,7 +110,7 @@ variables, like this:
110110
The story title and body templates are processed using the [Mustache](https://mustache.github.io/)
111111
templating system. It receives [the Payload object returned from the GitHub API](https://docs.github.com/en/free-pro-team@latest/developers/webhooks-and-events/webhook-events-and-payloads#pull_request). Note that you may want to use the triple mustache syntax to disable HTML escaping. Also Clubhouse supports full Markdown formatting, emojis, and @ mentions. Feel free to use them to your heart's desire. :heart_eyes_cat:
112112

113-
If you don't provide a title or body template, this action will simply use the Pull Request Title (`{{{ payload.pull_request.title }}}`) and Pull Request Body (`{{{ payload.pull_request.body }}}`) by default.
113+
If you don't provide a title or body template, this action will simply use the Pull Request Title (`{{{ payload.pull_request.title }}}`) and Pull Request Body (`{{{ payload.pull_request.body }}}`) by default.
114114

115115
## User Map
116116

@@ -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.5
130+
- uses: singingwolfboy/create-linked-clubhouse-story@v1.6
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.5
158+
- uses: singingwolfboy/create-linked-clubhouse-story@v1.6
159159
with:
160160
github-token: ${{ secrets.GITHUB_TOKEN }}
161161
clubhouse-token: ${{ secrets.CLUBHOUSE_TOKEN }}
@@ -165,7 +165,7 @@ Multiple users should be separated by commas.
165165

166166
## Only Users
167167

168-
You can also add a list of GitHub `only-users` for this integration. This works opposite of the ignored users list above. For example, if you wanted only PRs from a specific GitHub user such as dependabot PRs.
168+
You can also add a list of GitHub `only-users` for this integration. This works opposite of the ignored users list above. For example, if you wanted only PRs from a specific GitHub user such as dependabot PRs.
169169
Multiple users should be separated by commas.
170170

171171
```yaml

0 commit comments

Comments
 (0)