Label tracking meta-issue (edit me to get automatically CC'ed on issues!)

[carmocca]

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.

---

• aliasing @apaz-cli
• amp @crcrpar
• apex @crcrpar
• autograd
• benchmarking @crcrpar
• ci @Borda
• ci / tests @Borda
• code health @Borda
• complex
• constraints & caching
• crash @apaz-cli
• cuda @Borda
• cudagraphs
• cudnn
• debugging @apaz-cli
• dependencies @Borda
• deprecation @Borda
• design required @apaz-cli
• determinism
• developer efficiency @Borda @apaz-cli
• device modeling
• distributed @crcrpar
• docker @Borda
• documentation @Borda @apaz-cli
• examine @apaz-cli
• executors @apaz-cli
• extensibility @apaz-cli
• fusion logic
• gnns
• good first issue
• has conflicts
• high priority @apaz-cli
• install @Borda
• linting @Borda
• memory format
• MegatronImagen @tfogal
• module
• nemo @tfogal
• numbers
• numerical accuracy
• nvfuser @tfogal
• nvidia @tfogal
• onboarding @apaz-cli
• operators @apaz-cli
• optimization passes @apaz-cli
• packaging @Borda
• performance
• primitives
• printing
• profiling @riccardofelluga
• prototype
• pytree
• question @apaz-cli
• randomness @apaz-cli
• reductions
• rematerialization @riccardofelluga
• sdpa
• special
• strides
• testing @apaz-cli
• torch @apaz-cli
• torch.compile @apaz-cli
• torchex @apaz-cli
• tracing architecture @apaz-cli
• tracing time @apaz-cli
• tracker
• transforms
• triage review
• type promotion
• ux @Borda
• visualization @riccardofelluga
• vmap
• warnings & errors @apaz-cli
• wontfix
• zeroelem tensors

The current list of labels can be retrieved with $ gh label list --limit 1000 --json name --jq '.[] | "* " + .name' | sort -n