New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FormBrowse: let the user add fetch/pull custom icons in the toolbar #10293
FormBrowse: let the user add fetch/pull custom icons in the toolbar #10293
Conversation
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.
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.
+0
@@ -12,6 +12,8 @@ partial class FormBrowse | |||
{ | |||
// This file is dedicated to init logic for FormBrowse menus and toolbars | |||
|
|||
public const string PullShortcutsPrefix = "pull_shortcut_"; |
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.
public const string PullShortcutsPrefix = "pull_shortcut_"; | |
internal const string PullShortcutsPrefix = "pull_shortcut_"; |
b5ec77d
to
ce3ae45
Compare
Done. Should be merged after #10294 (because the settings save is based on the same code change, because the default value is 'false') |
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.
just nitpicks
I don't see a risk why these two PRs for toolbar buttons should not be integrated into v4.0.
756a928
to
438882d
Compare
Done.
Yes, that's not very risky PRs. But I think @RussKie was interested to have #10294 or #10235 merged in v4... |
da08947
to
c5f6942
Compare
Improvement over #3923
Proposed changes
Screenshots
Before
After
Configuration:
Result (because I want a fetch button distinct of a pull button --like in all the other git GUIs--):
Test methodology
Test environment(s)
Merge strategy
I agree that the maintainer squash merge this PR (if the commit message is clear).
✒️ I contribute this code under The Developer Certificate of Origin.