You can not select more than 25 topics Topics must start with a chinese character,a letter or number, can include dashes ('-') and can be up to 35 characters long.

command.md 6.0 kB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196
  1. ## MindSpore Community Command Help
  2. All of the projects in MindSpore Community are maintained by Bot.
  3. That means the developers can comment below every Pull Request or Issue to trigger Bot Commands.
  4. The Commands include the following:
  5. <table class="command">
  6. <thead>
  7. <tr>
  8. <th>Command</th>
  9. <th width="25%">Example</th>
  10. <th>Description</th>
  11. <th>Who Can Use</th>
  12. </tr>
  13. </thead>
  14. <tbody>
  15. <tr>
  16. <td>
  17. /check-cla
  18. </td>
  19. <td style="white-space:nowrap;">
  20. /check-cla
  21. </td>
  22. <td>
  23. Forces rechecking of the CLA status of a Pull Request.
  24. If the Pull Request author has already signed CLA,
  25. the label `mindspore-cla/yes` will be added in the Pull Request,
  26. If not, the label `mindspore-cla/no` will be added.
  27. </td>
  28. <td>
  29. Anyone
  30. </td>
  31. </tr>
  32. <tr>
  33. <td>
  34. /lgtm [cancel]
  35. </td>
  36. <td style="white-space:nowrap;">
  37. /lgtm
  38. <br/>
  39. /lgtm cancel
  40. </td>
  41. <td>
  42. Adds or removes the `lgtm` label which is typically used to gate merging.
  43. </td>
  44. <td>
  45. Collaborators on the repository. `/lgtm cancel` can be used additionally by the Pull Request author.
  46. </td>
  47. </tr>
  48. <tr>
  49. <td>
  50. /approve [cancel]
  51. </td>
  52. <td style="white-space:nowrap;">
  53. /approve
  54. <br/>
  55. /approve cancel
  56. </td>
  57. <td>
  58. Adds or removes the `approved` label which is typically used to gate merging.
  59. </td>
  60. <td>
  61. Collaborators on the repository.
  62. </td>
  63. </tr>
  64. <tr>
  65. <td>
  66. /[remove-]kind
  67. </td>
  68. <td style="white-space:nowrap;">
  69. /kind bug
  70. <br/>
  71. /remove-kind bug
  72. </td>
  73. <td>
  74. Applies or removes a kind label from one of the recognized types of labels.
  75. For example, the label is more like `kind/bug`.
  76. </td>
  77. <td>
  78. Anyone can trigger this command on a Pull Request or Issue.
  79. </td>
  80. </tr>
  81. <tr>
  82. <td>
  83. /[remove-]priority
  84. </td>
  85. <td style="white-space:nowrap;">
  86. /priority high
  87. <br/>
  88. /remove-priority high
  89. </td>
  90. <td>
  91. Applies or removes a priority label from one of the recognized types of labels.
  92. For example, the label is more like `priority/high`.
  93. </td>
  94. <td>
  95. Anyone can trigger this command on a Pull Request or Issue.
  96. </td>
  97. </tr>
  98. <tr>
  99. <td>
  100. /[remove-]sig
  101. </td>
  102. <td style="white-space:nowrap;">
  103. /sig kernel
  104. <br/>
  105. /remove-sig kernel
  106. </td>
  107. <td>
  108. Applies or removes a sig label from one of the recognized types of labels.
  109. For example, the label is more like `sig/kernel`.
  110. </td>
  111. <td>
  112. Anyone can trigger this command on a Pull Request or Issue.
  113. </td>
  114. </tr>
  115. <tr>
  116. <td>
  117. /close
  118. </td>
  119. <td style="white-space:nowrap;">
  120. /close
  121. </td>
  122. <td>
  123. Closes a Pull Request or an Issue.
  124. </td>
  125. <td>
  126. Authors and collaborators on the repository can trigger this command.
  127. </td>
  128. </tr>
  129. <tr>
  130. <td>
  131. /reopen
  132. </td>
  133. <td style="white-space:nowrap;">
  134. /reopen
  135. </td>
  136. <td>
  137. Reopens an Issue.
  138. </td>
  139. <td>
  140. Authors and collaborators on the repository can trigger this command.
  141. </td>
  142. </tr>
  143. <tr>
  144. <td>
  145. /retest
  146. </td>
  147. <td style="white-space:nowrap;">
  148. /retest
  149. </td>
  150. <td>
  151. Rerun test jobs that have failed.
  152. </td>
  153. <td>
  154. Anyone can trigger this command on a Pull Request.
  155. </td>
  156. </tr>
  157. <tr>
  158. <td>
  159. /assign [[@]...]
  160. </td>
  161. <td style="white-space:nowrap;">
  162. /assign
  163. <br/>
  164. /assign @mindspore-ci-bot
  165. </td>
  166. <td>
  167. Assigns an assignee to an Issue.
  168. </td>
  169. <td>
  170. Anyone can use this command on an Issue,
  171. but the target user must be a member of the org that owns the repository.
  172. If no target user is specified, that means this Issue will be assigned to yourself.
  173. </td>
  174. </tr>
  175. <tr>
  176. <td>
  177. /unassign [[@]...]
  178. </td>
  179. <td style="white-space:nowrap;">
  180. /unassign
  181. <br/>
  182. /unassign @mindspore-ci-bot
  183. </td>
  184. <td>
  185. UnAssigns an assignee from an Issue.
  186. </td>
  187. <td>
  188. Anyone can use this command on an Issue,
  189. but the target user must be a member of the org that owns the repository.
  190. If no target user is specified, that means this Issue will be unassigned from yourself.
  191. </td>
  192. </tr>
  193. </tbody>
  194. </table>