-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Conversation
I'd love to see some indication of whether the pull request is in a merge-able state. At the moment we know that ✔️ is definitely and ❌ is definitely not merge-able (assuming any restrictions are in place). Where we see a doughnut (💭 mmm doughnuts), we have no way of knowing whether the pull request is in a merge-able state. Crazy idea, could we color the center of the doughnut green or red, when we know the pull request is definitely merge-able or not merge-able? 😄 |
I pushed a small tweak adjusting the thickness of the donut chart so that it's closer to the line thickness of the octicons: This looks good to be merged in.
@jcansdale I'm hesitant on adding more information since we'll need to come up with an approach that's clear and can fit in the limited amount of space that we have. I struggled with this a bit with the annotation markers; and in the spirit of moving this pull request forward, I think it's best better to punt at this time. Would you be open to showing this type of information in the pull request detail view / sidebar? That way, we can breakdown why a branch isn't mergeable (out of date, review needed, required checks, etc) and guide developers to fix it: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great in general. Just a problem with how you're doing dependency properties.
My attempt to emulate this in Xaml
TODO:
Remove the summary checks from the View Model, if we decide not to use itIMAGE:
