Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add an explanation of subcommands #2699

Closed
wants to merge 2 commits into from
Closed

Add an explanation of subcommands #2699

wants to merge 2 commits into from

Conversation

baruchiro
Copy link
Contributor

@baruchiro baruchiro commented Jan 10, 2019

  • The page has 8 or fewer examples.
  • The PR title conforms to the recommended templates.

I searched for a record for a git checkout and nearly opened an issue on it.
I think if there is a user who is less engaged in open source, he would not know how to get records for subcommands.

@CLAassistant
Copy link

CLAassistant commented Jan 10, 2019

CLA assistant check
All committers have signed the CLA.

@sbrl sbrl added the page edit Changes to an existing page(s). label Jan 11, 2019

- For typical usages of a subcommand:

`tldr {{command-subcommand}}`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not true. You don't need the -. You can do "tldr git merge" and it works fine.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

$ tldr git merge
Invalid argument `merge'

Usage: tldr [-v|--version] [--update] COMMAND
  tldr Client program

Ubuntu 18.10

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is a client specific thing. The node client handles it fine. Since this is not in any spec, I don't think we should mention it.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So does the bash client. Perhaps you could open an issue against your client's repo?

(For my own reference, this is worth including in the official client spec that's being drafted in #1065)

pages/common/git.md Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
page edit Changes to an existing page(s).
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants