-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Label tracking meta-issue (edit me to get automatically CC'ed on issues!) #10530
Comments
@Borda do not lock the issue so that the community can request being added/removed. |
is it possible to configure the same for discussions as well? we have labels there. |
Probably yes, if GitHub triggers API events for discussions too |
Hey @carmocca , Could you remove @AyushExel from logger: wandb? |
Note that when a label occurs multiple times in the list above, the bottom one overrides the others and not all authors get included. I'm going to merge the two "docs" instances we currently have into one. |
@carmocca I cannot edit this issue. Would you please remove myself, @ninginthecloud, @edward-io, and @jjenniferdai from being tagged? thanks! |
@ananthsub done |
Added @JackCaoG @steventk-g and @Liyang90 to TPU accelerator label <3 Thank you for your help |
Hi @carmocca: Can you please remove @manangoel99 from logger:wandb and tag me instead? |
This issue is used by lightning-probot to manage subscriptions to labels. To subscribe yourself to a label, add a line
* label @yourusername
, or add your username to an existing line (space separated) in the body of this issue. Do not try to subscribe in comments, the bot only parses the initial post.This is a copy of pytorch/pytorch#24422.
As a courtesy to others, please do not edit the subscriptions of users who are not you.
Note: Some labels have sublabels (e.g. callback), but you won't be subscribing to them automatically if you choose the label at the top level.
PR status
Issue/PR category
Issue/PR severity
Issue/PR metadata
Generic labels
Code section (pl)
Feature (pl)
The text was updated successfully, but these errors were encountered: