Is your feature request related to a problem? Please describe.
There's a decent amount of inconsistency regarding where or when GSB is capitalized. The rule that should be followed is:
it's gsb when referring to the command, package or branch name, e.g.
gsb history -v
from gsb import _git
pipx install gsb
git checkout gsb
it's GSB when referring to the tool itself, e.g.
"To install GSB on your system..."
"No GSB-managed backups found."
Ambiguous:
Should the repo be https://github.com/OpenBagTwo/GSB? Ideally yes / more importantly https://OpenBagTwo.github.io/GSB/, but that URL already resolves correctly, so the normalization isn't a big concern.
Should it be GSB, version 0.0.2+32.g35ec027.dirty? Ideally, yes, but if Click makes that a hassle, it's not a big deal.
Describe the solution you'd like
Find all string occurrences of "gsb" (of any case) across the repo and docs
Ensure that each one follows the above style conventions
fix any tests that break (because they were expecting the wrong case)
note that these tests should be checking for the proper capitalization (and not performing case-insensitive regex)
Is your feature request related to a problem? Please describe.
There's a decent amount of inconsistency regarding where or when GSB is capitalized. The rule that should be followed is:
gsbwhen referring to the command, package or branch name, e.g.gsb history -vfrom gsb import _gitpipx install gsbgit checkout gsbhttps://github.com/OpenBagTwo/GSB? Ideally yes / more importantly https://OpenBagTwo.github.io/GSB/, but that URL already resolves correctly, so the normalization isn't a big concern.GSB, version 0.0.2+32.g35ec027.dirty? Ideally, yes, but if Click makes that a hassle, it's not a big deal.Describe the solution you'd like
Describe alternatives you've considered
Not caring?
Additional context