release notes script: keep not user facing rows #2875
Merged
+2
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Summary: We should keep the "not user facing" PRs in the draft release notes so that a human can go through them and verify they are actually not user facing. It's still easy to delete all of them from the generated file in a few seconds. Test Plan: Used this for v0.13.0 release notes formatting Reviewers: Subscribers: Tasks: Tags:
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/ao/2875
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 01718ff with merge base f3e549c ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
meta-cla
bot
added
the
CLA Signed
andrewor14
approved these changes
Aug 25, 2025
vkuzo
added
the
topic: not user facing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
We should keep the "not user facing" PRs in the draft release notes so that a human can go through them and verify they are actually not user facing. It's still easy to delete all of them from the generated file in a few seconds.
Test Plan:
Used this for v0.13.0 release notes formatting
Reviewers:
Subscribers:
Tasks:
Tags: