trunk/862dafe801376206e6f37dd27777701111550633: [GHF] Refresh reverted stack branches with the merge bot (#199717)
- PyTorch: 2501 events in the last 90 days
- PyTorch: 2468th Release in the last 90 days
- Previous: earlier the same day · trunk/17c3e6d45ef7a1473729299be9781f20fbea9f64: [GHF] Rebase GitHub-native PR stacks with the bot (#199716)
What happened
Impact: pytorchmergebot revert flow ( trymerge.py --revert ): after a non-ghstack revert has landed and reopened its PRs, it reads their stack and may push merge commits to their branches. PRs outside a stack, fork PRs and dry runs get no push and no comment Risk: low What After a stack revert, refresh_reverted_branches merges the default branch into the reverted PRs' branches with the rebase engine whenever merging…
Summary assembled by rule from the sources below