8000 Redirect mobile_optimizer.rst to executorch by svekars · Pull Request #153664 · pytorch/pytorch · GitHub
[go: up one dir, main page]
Skip to content

Redirect mobile_optimizer.rst to executorch #153664

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.

Sign up for GitHub

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

Jump to bottom
8000
Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Redirect mobile_optimizer.rst to executorch #153664

wants to merge 4 commits into from
+9 −17

Conversation

svekars
Copy link
Contributor
@svekars svekars commented May 15, 2025 •
edited by pytorch-bot bot
Loading

Redirect mobile_optimizer.rst to executorch

Fixes #ISSUE_NUMBER

cc @sekyondaMeta @AlannaBurke

@svekars
Redirect mobile_optimizer.rst to executorhc
3dbc722 
Redirect mobile_optimizer.rst to executorch
@svekars svekars added module: docs Related to our documentation, both in docs/ and docblocks topic: docs topic category labels May 15, 2025
@pytorch-bot PyTorch Bot
Copy link
pytorch-bot bot commented May 15, 2025 •
edited
Loading

🔗 Helpful Links

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

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

✅ No Failures

As of commit 40b340d with merge base e7a40fb (image):
💚 Looks good so far! There are no failures yet. 💚

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

@svekars svekars added the topic: not user facing topic category label May 15, 2025
@svekars svekars changed the title Redirect mobile_optimizer.rst to executorhc Redirect mobile_optimizer.rst to executorch May 15, 2025
@svekars svekars requested a review from cbilgin May 15, 2025 22:58
@svekars svekars requested a review from byjlw May 16, 2025 16:43
@svekars
Copy link
Contributor Author
svekars commented May 16, 2025

@pytorchbot merge -f "Docs only change, doc signal is green."

@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). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

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

@pytorchmergebot
Copy link
Collaborator

Merge failed

Reason: Approvers from one of the following sets are needed:

  • Documentation (svekars)
  • superuser (pytorch/metamates)
  • Core Reviewers (mruberry, lezcano, Skylion007, ngimel, peterbell10, ...)
  • Core Maintainers (soumith, gchanan, ezyang, dzhulgakov, malfet, ...)
Details for Dev Infra team Raised by workflow job

Failing merge rule: Core Maintainers

@svekars svekars requested a review from malfet May 16, 2025 17:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@byjlw byjlw byjlw approved these changes

@cbilgin cbilgin Awaiting requested review from cbilgin

@malfet malfet Awaiting requested review from malfet

Assignees
No one assigned
Labels
module: docs Related to our documentation, both in docs/ and docblocks topic: docs topic category topic: not user facing topic category
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@svekars @pytorchmergebot @byjlw
0