preview the number of commits that will be rebased#7167
Conversation
2b2b31c to
2e49bf8
Compare
0c62cd0 to
b519e06
Compare
56d51bb to
e4fd487
Compare
442a074 to
e98d9ea
Compare
5474ee6 to
6d8d555
Compare
Any clue how I might trip this state? I gather something like "branch at the same commit" might be a way to trigger this visual state? |
|
I've made a change in a83b297 that clarifies the UI and blocks the rebase from continuing - @tierninho let me know if you find new ways to break this path: |
|
So far looks good to me. 👍 |
Co-Authored-By: shiftkey <brendan@github.com>
Co-Authored-By: shiftkey <brendan@github.com>
@tierninho this is captured in #6960 and is on my radar for post-rebase-MVP |
niik
left a comment
There was a problem hiding this comment.
Just one tiny ask and then we can land this. Thanks for bearing with me
| border: solid transparent; | ||
| box-sizing: content-box; | ||
| position: relative; | ||
| z-index: 1; |
There was a problem hiding this comment.
I'm happy to leave this to someone with some bandwidth and CSS skills to figure out if it doesn't need to hold up this PR.
👍 Sounds good



Overview
Closes #6959
Description
Similar to the Merge Branch flow, the Rebase Flow now shows the number of commits that will be moved as part of the operation:
#6960 is tracking detecting conflicts at this stage, so for now this PR is focused on just the happy path and it's testing.
Some additional polish related to this area while I'm in here testing:
MergeStatusHeaderinto a generalized UI componentActionStatusIcon(lots of internals are hard-coded tomerge-status:emoji:Release notes
Notes: no-notes