You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently the recent section does not display once there are unmerged commits. This behavior is replicated from Magit, however the recent commit section still offers some value even when there are unmerged commits.
Ideally it would be great to have a config that allows from a persistent section. This can be disabled by default, so it doesn't change the default behavior.
Describe the solution you'd like
Add the option always = <boolean?> to the config.sections.recent table.
If this option is not set or set to false the recent section should only show when there is no unmerged commits (current behavior)
if this option is set to true the recent sections is always shown
I have a work branch of this change, PR incoming shortly.
Describe alternatives you've considered
N/A
Additional context
This options was briefly discussed in #1378
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently the recent section does not display once there are unmerged commits. This behavior is replicated from Magit, however the recent commit section still offers some value even when there are unmerged commits.
Ideally it would be great to have a config that allows from a persistent section. This can be disabled by default, so it doesn't change the default behavior.
Describe the solution you'd like
Add the option
always = <boolean?>
to theconfig.sections.recent
table.false
the recent section should only show when there is no unmerged commits (current behavior)true
the recent sections is always shownI have a work branch of this change, PR incoming shortly.
Describe alternatives you've considered
N/A
Additional context
This options was briefly discussed in #1378
The text was updated successfully, but these errors were encountered: