Pull requests show stale changes #179477
Replies: 1 comment
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Bug
Body
It often happens to me to apply a change on a branch (
dev) but I forget to push it.Then, I create a new branch (
feat) to introduce another change that origins fromdevand will go into that. This new branchfeatleads me to create a new Pull Request.So, as expected,
featshows both the change I didn't push yet ondevand the changes applied infeat.However, when I decide to push
dev, the Pull Request keeps showing the previously-not-pushed change as a changed that will get merged, while it shouldn't.I even tried to rebase
featontodevbut it didn't change.Beta Was this translation helpful? Give feedback.
All reactions