RFC: Push diffs in Git before telling GitHub about it#280
Merged
ezyang merged 1 commit intoezyang:masterfrom Mar 28, 2025
Merged
RFC: Push diffs in Git before telling GitHub about it#280ezyang merged 1 commit intoezyang:masterfrom
ezyang merged 1 commit intoezyang:masterfrom
Conversation
I ran into an issue reordering diffs in a direct stack (the one currently ending in pytorch/executorch#9586) where GitHub's API complained `There are no new commits between base branch 'gh/swolchok/395/head' and head branch 'gh/swolchok/383/head'`. This seems to have fixed it for me.
auto-merge was automatically disabled
March 27, 2025 15:37
Head branch was pushed to by a user without write access
swolchok
force-pushed
the
push-then-tell-github
branch
from
bed4f1b to
ff0e4a0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I ran into an issue reordering diffs in a direct stack (the one currently ending in pytorch/executorch#9586) where GitHub's API complained
There are no new commits between base branch 'gh/swolchok/395/head' and head branch 'gh/swolchok/383/head'. This seems to have fixed it for me.