Skip to content

Conversation

mergennachin
Copy link
Contributor

No description provided.

Copy link

pytorch-bot bot commented Oct 13, 2025

🔗 Helpful Links

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

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

❌ 3 New Failures, 5 Unrelated Failures

As of commit a774d1e with merge base d00279d (image):

NEW FAILURES - The following jobs have failed:

FLAKY - The following job failed but was likely due to flakiness present on trunk:

BROKEN TRUNK - The following jobs failed but was 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.

@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 Oct 13, 2025
Copy link

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

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

@mergennachin mergennachin force-pushed the update_main_readme branch 2 times, most recently from d2c291b to adb594f Compare October 13, 2025 15:49
Copy link
Contributor

@psiddh psiddh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Few links use /main/ branch, Looks like we need to explicitly update them to point to 1.0 branch when this gets cherry-picked

@mergennachin mergennachin merged commit 1a8acf6 into main Oct 13, 2025
126 of 134 checks passed
@mergennachin mergennachin deleted the update_main_readme branch October 13, 2025 16:49
mergennachin added a commit that referenced this pull request Oct 13, 2025
GregoryComer added a commit that referenced this pull request Oct 14, 2025
```
python scripts/pick_doc_commits.py --main=origin/main --release=origin/release/1.0
```

https://gist.github.com/mergennachin/155d28c84069d7808469ebaeca07aa5f


Cherry-picking


  - 42e8746 Update Voxral README.md (#14324)
  - 4d0961e Update Voxtral README.md (#14414)
  - 30568d2 Fix outdated lintrunner directions (#14449)
  - c98079a Update Voxtral README.md (#14544)
  - e608a21 [Backend Tester] Update README (#14739)
  - fc512fa Fix typos in docs ahead of GA (#14964)
  - 1a8acf6 Update top-level README.md file (#15049)
  - 9560800 Fix documentation link for Core ATen operators (#15050)
  - b9451c9 Use new logo in ExecuTorch (#14782)
  - 481c9cf Fix various minor links in top-level README.md (#15052)

 

Skipping

  - d382f6b mypy fix (#15080) (not a doc)
- 41b061e NXP backend: Update user guide and docs Readme (#14852)
(merge conflict)

---------

Co-authored-by: Jack <32371937+jackzhxng@users.noreply.github.com>
Co-authored-by: Scott Wolchok <swolchok@meta.com>
Co-authored-by: Gregory Comer <gjcomer@meta.com>
Co-authored-by: Abhinayk <abhinayk@meta.com>
@psiddh
Copy link
Contributor

psiddh commented Oct 14, 2025

@pytorchbot cherry-pick --onto release/1.0 -c docs

pytorchbot pushed a commit that referenced this pull request Oct 14, 2025
@pytorchbot
Copy link
Collaborator

Cherry picking #15049

The cherry pick PR is at #15115 The following tracker issues are updated:

Details for Dev Infra team Raised by workflow job

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants