Separate Test Token for Conda Uploads #3582
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/audio/3582
Note: Links to docs will display an error until the docs builds have been completed. ⏳ No Failures, 11 PendingAs of commit b0cffca with merge base 5ee254e ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
We will use a separate `CONDA_PYTORCHBOT_TOKEN_TEST` for using in a test environment Fixes #4529 TODO: 1. Add the token to the other domain repos 2. Add to audio caller: pytorch/audio#3582 3. Add to vision caller: pytorch/vision#7900
|
@osalpekar has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
|
@osalpekar merged this pull request in 6fb6854. |
|
Hey @osalpekar. Some guidance:Use 'module: ops' for operations under 'torchaudio/{transforms, functional}', and ML-related components under 'torchaudio/csrc' (e.g. RNN-T loss). Things in "examples" directory:
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, 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. 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'. Things related to build are by default excluded from the release note, except when it impacts users. For example: |
We will use a separate token for uploading test binaries (instead of reusing the nightly token). This PR adds that token to the caller workflow.