Open
Conversation
hsnabszhdn
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Heads-up: Potentially a spicy topic (open to discussion and even rejection)
Although the Git logo is all lowercase, i.e. "git", the textual representation of the project is "Git":
When used as a general text, it should be used like this:
When used as a CLI command, it should be used like this (lowercase backtick'd):
To see proper examples, search for
gitin the official Git - Getting a Git Repository document to see what I mean.I understand that both "git" and "Git" are generally used in online articles or product documentations. However, the usage here is an expert-written formal spec and standard.
I believe it should reflect professionalism and attention to details, and not follow the general "what everyone else does" pattern, but again it's more of a personal opinion than what's "right" or "wrong". So, up to the maintainers what to do with this PR...
⚖️ Disclaimer: I'm not a lawyer and it's not a legal advice. I'm just an engineer talking based on what I've seen/read around the Internet. It's up to the core maintainers to consider proper use and permissions of all trademarks. I take no responsibility for copyright infringements, trademark usage violations, or any financial/collateral damage (if any).