Move recently-pushed branches to the side - #869
Conversation
👍 Then we should also reverse the order (move the most recently pushed one to the top) |
|
I think handling well just a single branch is good enough :) |
73eb106 to
d28232b
Compare
|
One thing I found out: disabling the feature by adding The better description of this feature would be that it moves the notifications to floating panels and adds those panels to other pages like issues and PRs. |
|
The feature of this PR is CSS-based and can't be disabled. |
|
Thanks, understood, disabling the "feature" but keeping the styles is actually a perfect fit for me. As a complete side note, I was thinking that maybe it would be nice if features were implemented by adding some CSS classes to DOM via feature's javascript, and then CSS in At the same time, I'm super-happy that feature disablability is in Refined GitHub in the first place. Last time I tried to use it (sometime last year I think) there were too many decisions that actually made the experience worse for me. The new system is both simple and goes a very long way towards customizability, so I'm happy overall. |
|
Refer to #988 (comment) |




Closes #851
Here's how it looks with more than one branch:
Not great, considering it hides other content. Possible solutions:
xbutton to close it