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

[maskedtensor] fix docs formatting #87387

Closed
wants to merge 2 commits into from

Conversation

george-qi
Copy link
Contributor

@george-qi george-qi commented Oct 20, 2022

Stack from ghstack (oldest at bottom):

@pytorch-bot
Copy link

pytorch-bot bot commented Oct 20, 2022

🔗 Helpful Links

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

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

❌ 3 Failures

As of commit de57e95:

The following jobs have failed:

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

george-qi added a commit that referenced this pull request Oct 20, 2022
ghstack-source-id: 36f66f0f59b2755b6d5e68a01095914aa36df9fa
Pull Request resolved: #87387
george-qi added a commit that referenced this pull request Oct 20, 2022
ghstack-source-id: 6c235c736dca1bb7b19d18471299c690ced8d2ff
Pull Request resolved: #87387
@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Oct 20, 2022
@george-qi
Copy link
Contributor Author

@pytorchbot merge -f "Trivial docs typo fix"

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

@github-actions
Copy link

Hey @george-qi.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.

@cpuhrsch cpuhrsch added the topic: docs topic category label Oct 20, 2022
george-qi added a commit that referenced this pull request Oct 20, 2022
atalman pushed a commit that referenced this pull request Oct 21, 2022
sgrigory pushed a commit to sgrigory/pytorch that referenced this pull request Oct 28, 2022
@facebook-github-bot facebook-github-bot deleted the gh/george-qi/45/head branch June 8, 2023 17:19
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 Merged topic: docs topic category
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants