crane/gcrane: add pages

[rvandernoort]

closes #13664

• The page(s) are in the correct platform directories: common, linux, osx, windows, sunos, android, etc.
• The page(s) have at most 8 examples.
• The page description(s) have links to documentation or a homepage.
• The page(s) follow the content guidelines.
• The PR title conforms to the recommended templates.
• Version of the command being documented (if known):
  • crane: v0.20.2
  • gcrane: v0.20.1

[CLAassistant]

All committers have signed the CLA.

[sebastiaanspeck]

#13808 also adds crane.md. I have added some suggestions to the crane.md in this PR since it is more detailed.

[sebastiaanspeck]

First of all, thank you for the amazing work you put into this! Always great to have a first-contributor on board.

I have reviewed upon crane-index-filter.md, but those comments also apply to the rest of the files.

• Generally we put Display help and Display version as last commands (https://github.com/tldr-pages/tldr/blob/main/contributing-guides/style-guide.md#help-and-version-commands).
• A single option, e.g. --help, does not to be enclosed in {{...}}, only placeholders and short/long options {{-h|--help}}`.
• I also see a lot of {{strings}}, please be more descriptive what the string represents, a tag name, a filepath etc.
• If you can have more than 1 argument, please use {{argument1, argument2 ...}}.

[rvandernoort]

Hi thanks for the extensive review. I'll implement your feedback after the weekend and then we can hopefully merge soon after! Cheers

[rvandernoort]

Hi I've updated the PR according to the guidelines and your feedback can you take another look? Furthermore, as the bot indicates I've added the various implementations of gcrane completion which has some OS specific commands, I hope I correctly implemented that aspect.

[tldr-bot]

Hello! I've noticed something unusual when checking this PR:

• The page pages/linux/gcrane-completion.md already exists in the common directory.
• The page pages/osx/gcrane-completion.md already exists in the common directory.
• The page pages/windows/gcrane-completion.md already exists in the common directory.

Is this intended? If so, just ignore this comment. Otherwise, please double-check the commits.

[tldr-bot]

Hello! I've noticed something unusual when checking this PR:

• The page pages/linux/gcrane-completion.md already exists in the common directory.
• The page pages/osx/gcrane-completion.md already exists in the common directory.
• The page pages/windows/gcrane-completion.md already exists in the common directory.

Is this intended? If so, just ignore this comment. Otherwise, please double-check the commits.

[tldr-bot]

Hello! I've noticed something unusual when checking this PR:

• The page pages/linux/gcrane-completion.md already exists in the common directory.
• The page pages/osx/gcrane-completion.md already exists in the common directory.
• The page pages/windows/gcrane-completion.md already exists in the common directory.

Is this intended? If so, just ignore this comment. Otherwise, please double-check the commits.

[sebastiaanspeck]

Besides the extra comments, reviewing is easier if you do not force push the branch. That way we can see the changes per commit, especially if it is a large PR like this.

[rvandernoort]

Ah yes sorry, I though rebasing the branch with main was the way to go, but I get that this complicates the review. I've updated your last comments.

[sebastiaanspeck]

Ah yes sorry, I though rebasing the branch with main was the way to go, but I get that this complicates the review. I've updated your last comments.

The easiest is a merge, which can also be performed from the PR-site itself: