git-var: add page

[bl-ue]

• The page (if new), does not already exist in the repo.
• The page is in the correct platform directory (common/, linux/, etc.)
• The page has 8 or fewer examples.
• The PR title conforms to the recommended templates.
• The page follows the content guidelines.
• The page description includes a link to documentation or a homepage (if applicable).

For #3953

[sbrl]

Thanks for the new page! I've left a comment below for you to review.

[schneiderl]

@bl-ue PR looks good but I have a question: in which context those commands that you have opened PRs for are used? It looks like most of the functionality can be achieved by using "git" and its subcommands.

[sbrl]

Looks ok to me after @navarroaxel's comment is addressed

[bl-ue]

@schneiderl I didn't see your comment!

@bl-ue PR looks good but I have a question: in which context those commands that you have opened PRs for are used? It looks like most of the functionality can be achieved by using "git" and its subcommands.

Yes, I know that, and with commands like git commit-tree and git var it starts to feel a little silly :D but I decided to keep doing it (1) just for the sake of completeness and (2) so that users can know a little about the command—and what to look for instead.

Do you agree?

[schneiderl]

@bl-ue Agreed. I don't think we are the ones who decide which commands our user will use. Our job is to have everything documented as good as possible. 😄
Thank you for the job you've been doing here over the past weeks.