3 ms·
The author suggest prepending v to a tag name for the sake of shell completion. This assumes that everyone will be interacting with git tags using a shell. I di
by CamelRocketFish 4y ago
The author suggest prepending v to a tag name for the sake of shell completion. This assumes that everyone will be interacting with git tags using a shell. I disagree that a v should be prepended for that reason.
- silverwind 4y agoYes, this practice of adding a v is common, yet pointless. I prefer my git tags to be valid semvers.
- wnoise 4y agoThis works iff you never want to tag anything but semvers. This is an unusual and strict policy. As soon as you want the ability to move outside this you need something like namespacing. Prepending v is a pretty lightweight way to do this.
- inetknght 4y ago> The author suggest prepending v to a tag name for the sake of shell completion. This assumes that everyone will be interacting with git tags using a shell. I would argue that any tool (such as a GUI app) which doesn't provide the depth of usability that a shell offers is, in fact, a deficiency in the GUI or tool. If your GUI doesn't offer completions similar to a shell then your GUI tool is inferior to a shell.
- V-2 4y agoThis is usually the case. GUIs are superior in some aspects (eg. visualization of complex branch structures), inferior in others (eg. add more friction - many operations can be done faster from the console). As far as Git goes, I see GUI clients as complementary rather than full-scale substitute for the terminal.
- Tyr42 4y agoGitHub let's you do a partial filter. So it helps there too.