-
Notifications
You must be signed in to change notification settings - Fork 29.9k
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
should the commit button be hidden when there are no staged changes? #153707
Comments
At first I thought greying out the button would be a more consistent approach, but this could both be made unintuitive accessibility- and theme-wise, so hiding until staging is done is best. |
One thing to keep in mind is that depending on user settings one can commit changes that are not yet staged. Next milestone I will take a look at the various settings and I will factor in the settings value in the logic that displays the commit action button. |
this would address 👍 |
@meganrogge, could you please share the following user settings:
|
Not sure what they were when i encountered this (probably whatever is specified in the TPI), but they're currently
|
Thanks! The TPI does not mention any of the smart commit settings so I will assume that the state of these settings was the same. Even though you have If both |
The
|
@lszomoru could it be hide entirely(not just disable) when git.enableSmartCommit === false && git.suggestSmartCommit === false and show them when there are staged files |
@heartacker, I will continue to monitor customer feedback and will adjust the behaviour accordingly. |
Testing #153317
I noticed this bc the button made me think that I had forgotten to commit changes I had staged
The text was updated successfully, but these errors were encountered: