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.
This PR was created by the merge bot to help merge the original PR into the main branch.
ghstack PR number: #6265
^ Please use this as the source of truth for the PR number to reference in comments
ghstack PR base: https://github.com/pytorch/executorch/tree/gh/kirklandsign/12/base
ghstack PR head: https://github.com/pytorch/executorch/tree/gh/kirklandsign/12/head
Merge bot PR base: https://github.com/pytorch/executorch/tree/main
Merge bot PR head: https://github.com/pytorch/executorch/tree/gh/kirklandsign/12/orig
Original PR body:
gh/user/1/base <- gh/user/1/headwhere the PR is created like thismain <- gh/user/1/origThe purpose of this bot is, when the ghstack PR is merged, automatically create another PR to do this merge
main <- gh/user/1/orig. Then we just merge the newly created PR so thatmainhas that change.Missing piece: token from pytorch bot to create PR.
If this goes well, we can either
git mergethe commit from gh/user/1/orig into main directly, without going through the new PR; or auto approve and merge the PR.Test: You can test locally with
export GITHUB_TOKEN=ghpxyz; python .github/scripts/propose_ghstack_orig_pr.py --pr 6265 --repo pytorch/executorchNote that between /orig merges, there is never a merge conflict.
The invariant is guaranteed that gh/user/1/orig contains the exact same change between
gh/user/1/base <- gh/user/1/headby ghstack tool.Stack from ghstack (oldest at bottom):