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
Based on StackOverflow post about editable commit message in vscode the entire commit action should be changed in order to use a full editor. This will consolidate the user experience when using git from command line and configuring vscode as preferred editor.
There is no treason to have a different editing experiences for the two cases. In fact is a bit ironic that editing the commit message is much better when git calls vscode than using vscode directly. This enables spellchecking, linting, syntax checks like 50/72 rule and a ton of other features which are not available in the crippled input box of the default commit feature.
The text was updated successfully, but these errors were encountered:
Based on StackOverflow post about editable commit message in vscode the entire commit action should be changed in order to use a full editor. This will consolidate the user experience when using git from command line and configuring vscode as preferred editor.
There is no treason to have a different editing experiences for the two cases. In fact is a bit ironic that editing the commit message is much better when git calls vscode than using vscode directly. This enables spellchecking, linting, syntax checks like 50/72 rule and a ton of other features which are not available in the crippled input box of the default commit feature.
The text was updated successfully, but these errors were encountered: