Skip to content

Commit 96c10bb

Browse files
authored
Fixed inaccurate PR labelling instructions (#10268)
### Summary Previously, the new contributor guide claimed non-maintainers couldn't label their PRs. This update fixes that, providing instructions on how to make pytorchbot to add a label. Co-authored-by: jhels <[email protected]>
1 parent 8f29aa9 commit 96c10bb

File tree

3 files changed

+9
-1
lines changed

3 files changed

+9
-1
lines changed
Loading
Loading

docs/source/new-contributor-guide.md

+9-1
Original file line numberDiff line numberDiff line change
@@ -253,7 +253,15 @@ Once you've successfully finished local development, it's time to send out your
253253
254254
![](_static/img/new-contributor-guide/release_notes.png)
255255
256-
Please ignore this message. It's directed at the ExecuTorch maintainers — they'll label your PR for you.
256+
As the comment says, you can add a label by commenting on the PR with an instruction to pytorchbot. You can see a list of all our labels [here](https://github.com/pytorch/executorch/labels/). Pick the one which fits your PR best, then add it as a comment using the syntax `@pytorchbot label "YOUR LABEL HERE"`. For example:
257+
258+
![](./_static/img/new-contributor-guide/how_to_label1.png)
259+
260+
After you've submitted your comment, `pytorchbot` will add your chosen label to the PR:
261+
262+
![](./_static/img/new-contributor-guide/how_to_label2.png)
263+
264+
and the `github-actions` comment requesting a label will disappear.
257265
258266
* At the end of your Draft PR, you'll see something like this:
259267

0 commit comments

Comments
 (0)