Commit c51f20f9 authored by moto's avatar moto Committed by Facebook GitHub Bot
Browse files

Fix lint and format PR label message (#3299)

Summary: Pull Request resolved: https://github.com/pytorch/audio/pull/3299

Reviewed By: xiaohui-zhang

Differential Revision: D45530945

Pulled By: mthrok

fbshipit-source-id: 3443e4de693898534687b26ee1a9376ff86651f9
parent 76f91135
...@@ -75,25 +75,36 @@ def post_github_comment(pr_number: int, merger: str) -> Any: ...@@ -75,25 +75,36 @@ def post_github_comment(pr_number: int, merger: str) -> Any:
+ """ + """
You merged this PR, but labels were not properly added. Please add a primary and secondary label \ You merged this PR, but labels were not properly added. Please add a primary and secondary label \
(See https://github.com/pytorch/audio/blob/main/.github/process_commit.py). (See https://github.com/pytorch/audio/blob/main/.github/process_commit.py).
Some guidance:
---
## Some guidance:
Use 'module: ops' for operations under 'torchaudio/{transforms, functional}', \ Use 'module: ops' for operations under 'torchaudio/{transforms, functional}', \
and ML-related components under 'torchaudio/csrc' (e.g. RNN-T loss). and ML-related components under 'torchaudio/csrc' (e.g. RNN-T loss).
Things in "examples" directory: Things in "examples" directory:
'recipe' is applicable to training recipes under the 'examples' folder, - 'recipe' is applicable to training recipes under the 'examples' folder,
'tutorial' is applicable to tutorials under the “examples/tutorials” folder - 'tutorial' is applicable to tutorials under the “examples/tutorials” folder
'example' is applicable to everything else (e.g. C++ examples) - 'example' is applicable to everything else (e.g. C++ examples)
'module: docs' is applicable to code documentations (not to tutorials). \ - 'module: docs' is applicable to code documentations (not to tutorials). \
Regarding examples in code documentations, please also use 'module: docs'.
Regarding examples in code documentations, please also use 'module: docs'.
Please use 'other' tag only when you’re sure the changes are not much relevant to users, \ Please use 'other' tag only when you’re sure the changes are not much relevant to users, \
or when all other tags are not applicable. Try not to use it often, in order to minimize \ or when all other tags are not applicable. Try not to use it often, in order to minimize \
efforts required when we prepare release notes. efforts required when we prepare release notes.
---
When preparing release notes, please make sure 'documentation' and 'tutorials' occur as the \ When preparing release notes, please make sure 'documentation' and 'tutorials' occur as the \
last sub-categories under each primary category like 'new feature', 'improvements' or 'prototype'. last sub-categories under each primary category like 'new feature', 'improvements' or 'prototype'.
Things related to build are by default excluded from the release note, except when it impacts users.
For example: Things related to build are by default excluded from the release note, \
except when it impacts users. For example:
* Drop support of Python 3.7. * Drop support of Python 3.7.
* Add support of Python 3.X. * Add support of Python 3.X.
* Changing the way a third party library is bound (so that user needs to install it separately). * Change the way a third party library is bound (so that user needs to install it separately).
""" """
} }
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment