lambo, lambo-new: add page

[owenvoke]

• 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).

[bl-ue]

Is there a reason why you sometimes use = in flags but sometimes not?
Like this:

lambo new --path={{path/to/directory}} {{name}}

lambo new --auth {{name}}

[owenvoke]

@bl-ue, because the ones without an equals sign don't have a value (they are a boolean value). Whereas the ones with = need a value.

[bl-ue]

Seems like an obvious one now. 😄 I wish I could laugh at that 5 times :D

[navarroaxel]

I think this should be move to lambo-new.md and create a lambo.md for --help, edit-config, make-after, edit-after and the simplest lambo new subcommands.

[navarroaxel]

Hey @owenvoke, do you think this is not useful? #5139 (review)

[owenvoke]

Apologies @navarroaxel, I missed that comment. I'm not entirely sure that this would be necessary. 🤔

[bl-ue]

I'm inclined to agree with @navarroaxel, because what about the other lambo subcommands like edit-config, make-after , and edit-after? Just because they may not be very useful/used often doesn't mean we shouldn't document them, you know.

[owenvoke]

Fair enough, I was just showing the most used commands that are the whole purpose of the tool. For reference make-after no longer exists as it's irrelevant, and there isn't a --help flag (it's displayed when no command or directory is specified). But I've added now split it into another page with the other commands.

[bl-ue]

Oh cool! I didn't notice lambo in addition to lambo-new 😄

Thank you @owenvoke!