Skip to content

docs: fix duplicate conclusion labels#3870

Merged
jerryzh168 merged 1 commit intopytorch:mainfrom
ArivunidhiA:fix/docs-duplicate-labels-part2
Feb 13, 2026
Merged

docs: fix duplicate conclusion labels#3870
jerryzh168 merged 1 commit intopytorch:mainfrom
ArivunidhiA:fix/docs-duplicate-labels-part2

Conversation

@ArivunidhiA
Copy link
Contributor

Add unique reference labels for conclusion sections to resolve autosectionlabel conflicts:

  • Add serving-conclusion label (eager_tutorials/serving.rst)
  • Add pt2e_quant_xpu_inductor-conclusion label
  • Add pt2e_quantizer-conclusion label
  • Add pt2e_quant_ptq-conclusion label
  • Add pt2e_quant_openvino_inductor-conclusion label
  • Add pt2e_quant_qat-conclusion label
  • Add pt2e_quant_x86_inductor-conclusion label

Resolves 7 duplicate conclusion label warnings from issue #3863

Add unique reference labels for conclusion sections:

- Add serving-conclusion label (eager_tutorials/serving.rst)
- Add pt2e_quant_xpu_inductor-conclusion label
- Add pt2e_quantizer-conclusion label
- Add pt2e_quant_ptq-conclusion label
- Add pt2e_quant_openvino_inductor-conclusion label
- Add pt2e_quant_qat-conclusion label
- Add pt2e_quant_x86_inductor-conclusion label

Resolves 7 duplicate 'conclusion' label warnings from issue pytorch#3863 (Category 2)
@pytorch-bot
Copy link

pytorch-bot bot commented Feb 12, 2026

🔗 Helpful Links

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

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

✅ No Failures

As of commit 06e3d1d with merge base edd8abb (image):
💚 Looks good so far! There are no failures yet. 💚

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

@meta-cla
Copy link

meta-cla bot commented Feb 12, 2026

Hi @ArivunidhiA!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

@meta-cla
Copy link

meta-cla bot commented Feb 12, 2026

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@meta-cla meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Feb 12, 2026
@meta-cla
Copy link

meta-cla bot commented Feb 12, 2026

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@jerryzh168 jerryzh168 added the topic: documentation Use this tag if this PR adds or improves documentation label Feb 12, 2026
@jerryzh168 jerryzh168 merged commit 94df7db into pytorch:main Feb 13, 2026
24 checks passed
@jerryzh168 jerryzh168 added module: not user facing module: not user facing Use this tag if you don't want this PR to show up in release notes labels Feb 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. module: not user facing Use this tag if you don't want this PR to show up in release notes topic: documentation Use this tag if this PR adds or improves documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants