Skip to content

Commit ee6eb6d

Browse files
authored
Refine text for referencing (#13176)
* Refine text for referencing * Shorten comment text
1 parent 38ba42b commit ee6eb6d

File tree

1 file changed

+2
-18
lines changed

1 file changed

+2
-18
lines changed

.github/ghprcomment.yml

Lines changed: 2 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -144,29 +144,13 @@
144144
- jobName: 'Determine issue number'
145145
always: true
146146
message: |
147-
Your pull request needs to link an issue.
147+
Your pull request needs to link an issue correctly.
148148
149149
To ease organizational workflows, please link this pull-request to the issue with syntax as described in <https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue>:
150150
151151
> <h2 id="linking-a-pull-request-to-an-issue-using-a-keyword">Linking a pull request to an issue using a keyword</h2>
152152
> <p>You can link a pull request to an issue by using a supported keyword
153-
> in the pull request's description or in a commit message. The pull
154-
> request <strong>must be</strong> on the default branch.</p>
155-
> <ul>
156-
> <li>close</li>
157-
> <li>closes</li>
158-
> <li>closed</li>
159-
> <li>fix</li>
160-
> <li>fixes</li>
161-
> <li>fixed</li>
162-
> <li>resolve</li>
163-
> <li>resolves</li>
164-
> <li>resolved</li>
165-
> </ul>
166-
> <p>If you use a keyword to reference a pull request comment in another
167-
> pull request, the pull requests will be linked. Merging the referencing
168-
> pull request also closes the referenced pull request.</p>
169-
> <p>The syntax for closing keywords depends on whether the issue is in the same repository as the pull request.</p>
153+
> in the pull request's description or in a commit message.
170154
171155
### Examples
172156

0 commit comments

Comments
 (0)