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
Using this extension it is possible to create an annotated tag without message by not filling message field. However i can't reproduce this using git command, it just fails with 'fatal' message. I've investigated and found in "Output" tab that extension runs command git tag -a <tag name> -m <commit hash>, but this command also doesn't work. So, how this is implemented and how it can be done without this extension?
The text was updated successfully, but these errors were encountered:
It depends on what terminal you use, but running git tag -a <tag name> -m "" <commit hash> in the Windows Command Prompt will produce an annotated tag without a message. I expect all other shells will have a way to specify an empty string argument.
Internally, the extension spawns a child process to execute each Git command, which accepts all of the command arguments as an array of strings (e.g. ["tag", "-a", "<tag name>", "-m", "<message>", "<commit hash>"]) - which nicely handles empty strings and avoids escaping issues. The Git Graph Output Channel displays the executed commands by simply joining all these arguments with a space separator, hence the current behaviour with an empty message, and the double space between -m & <commit hash>.
I'll adjust the Output Channel to explicitly display empty string arguments as "" in the next release, to make it clearer.
Using this extension it is possible to create an annotated tag without message by not filling message field. However i can't reproduce this using git command, it just fails with 'fatal' message. I've investigated and found in "Output" tab that extension runs command
git tag -a <tag name> -m <commit hash>
, but this command also doesn't work. So, how this is implemented and how it can be done without this extension?The text was updated successfully, but these errors were encountered: