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

treehouses message gitter inside of README.md should be formatted correctly #2050

Closed
rjpadilla opened this issue Feb 27, 2021 · 0 comments
Closed

Comments

@rjpadilla
Copy link
Member

The message gitter inside of README.md should be separated (there is no stand-alone command for treehouses message gitter) to its own line.

cli/README.md

Line 168 in 9221064

message gitter <apitoken|authorize> sets api/channel info in config file and sends/recieves messages in gitter


message should be in its own stand-alone line.


The subcommands for message:

  • gitter
  • slack
  • discord

should all be wrapped by <> brackets.

cli/README.md

Lines 168 to 173 in 9221064

message gitter <apitoken|authorize> sets api/channel info in config file and sends/recieves messages in gitter
<send|show|read|mark>
<channels>
slack <apitoken|channels> sets api/channel info in config file and sends/recieves messages in slack
<send|show|read|mark>
discord <apitoken|authorize> sets api/channel info in config file

The magazine subcommand from Lines 159 to 165 should be the ideal format for the message subcommand.

cli/README.md

Lines 159 to 165 in 9221064

magazines downloads specific magazine issue as a pdf based on user input
<available|downloaded> lists the available magazine types, lists downloaded magazines in a tree format
<helloworld> [all] downloads all issues of magazine
<hackspace> [latest] downloads latest issue of magazine
<magpi> [number] downloads issue [number] of magazine
<wireframe> [list] lists downloaded magazines in tree format of specific magazine
[url] shows the homepage URL of magazine

rjpadilla added a commit that referenced this issue Feb 27, 2021
rjpadilla added a commit that referenced this issue Mar 13, 2021
@dogi dogi closed this as completed in 7efa362 Mar 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant