Skip to content
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

Fix the specific setting in documentation to match with elsewhere #124463

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

lsb
Copy link

@lsb lsb commented Apr 19, 2024

Twenty lines lower and thirty lines lower the submodules are correct

Twenty lines lower and thirty lines lower the submodules are correct
Copy link

pytorch-bot bot commented Apr 19, 2024

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/124463

Note: Links to docs will display an error until the docs builds have been completed.

✅ You can merge normally! (1 Unrelated Failure)

As of commit 83cdab7 with merge base b2f6cfd (image):

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

This comment was automatically generated by Dr. CI and updates every 15 minutes.

Copy link

linux-foundation-easycla bot commented Apr 19, 2024

CLA Signed


The committers listed above are authorized under a signed CLA.

@colesbury
Copy link
Member

@pytorchbot merge

Copy link

pytorch-bot bot commented Apr 22, 2024

Pull workflow has not been scheduled for the PR yet. It could be because author doesn't have permissions to run those or skip-checks keywords were added to PR/commits, aborting merge. Please get/give approval for the workflows and/or remove skip ci decorators before next merge attempt. If you think this is a mistake, please contact PyTorch Dev Infra.

@colesbury
Copy link
Member

@pytorchbot merge

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Apr 22, 2024
@pytorchmergebot
Copy link
Collaborator

Merge failed

Reason: This PR needs a release notes: label
If your changes are user facing and intended to be a part of release notes, please use a label starting with release notes:.

If not, please add the topic: not user facing label.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "topic: not user facing"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

Details for Dev Infra team Raised by workflow job

@lsb
Copy link
Author

lsb commented Apr 27, 2024

@pytorchbot label "topic: documentation, quantization"

Copy link

pytorch-bot bot commented Apr 27, 2024

Didn't find following labels among repository labels: topic: documentation, quantization

@lsb
Copy link
Author

lsb commented Apr 27, 2024

@pytorchbot label "topic: documentation"

Copy link

pytorch-bot bot commented Apr 27, 2024

Didn't find following labels among repository labels: topic: documentation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ciflow/trunk Trigger trunk jobs on your pull request open source
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants