mirror of https://github.com/danbulant/nushell synced 2026-06-10 02:00:23 +00:00

History

sebastian-xyz f4dc79f4ba add group-by command documentation		2019-11-16 15:31:28 +01:00
..
add.md
append.md	Add append command documentation	2019-11-15 15:37:41 +01:00
average.md	fix typos and incorrect commands	2019-10-18 20:43:37 -04:00
cd.md	Add documentation for `cd -`	2019-10-08 18:32:42 +11:00
count.md	Add docs for the count command	2019-11-10 14:12:59 +05:30
date.md
echo.md
edit.md
enter.md	Add documentation for the enter command	2019-10-07 23:21:58 +08:00
env.md
exit.md
fetch.md
first.md
from-csv.md	Add --separator command to from_csv	2019-11-08 15:06:33 +00:00
from-toml.md	Create docs for from-toml command	2019-10-25 20:47:00 +02:00
group-by.md	add group-by command documentation	2019-11-16 15:31:28 +01:00
help.md
inc.md
last.md
lines.md
nth.md
open.md
pick.md	Add documentation for the pick and reject command	2019-11-10 12:37:27 +05:30
pivot.md	Document pivot command	2019-11-14 16:59:39 -05:00
prepend.md	Add prepend command documentation	2019-11-15 15:53:58 +01:00
README.md
reject.md	Add documentation for the pick and reject command	2019-11-10 12:37:27 +05:30
reverse.md
shells.md
size.md	Make documentation for size command	2019-11-10 14:41:23 +05:30
sort-by.md	added Docs for sort-by command	2019-10-21 17:59:20 +02:00
str.md	Updated Doc, error on bad input	2019-11-01 17:25:08 -05:00
sum.md	fix typos and incorrect commands	2019-10-18 20:43:37 -04:00
sys.md
tags.md	Add documentation for tags command	2019-11-01 00:08:24 -04:00
to-csv.md
to-json.md
to-toml.md
to-tsv.md
to-url.md
to-yaml.md
trim.md
version.md
where.md

README.md

How do I get started?

Pick any command from the checklist and write a comment acknowledging you started work.

Instructions for documenting a Nu command of your choosing

Name the file after the command, like so:

command.md

Example: If you want to add documentation for the Nu command enter, create a file named enter.md, write documentation, save it at /docs/commands/[your_command_picked].md as and create your pull request.

What kind of documentation should I write?

Anything you want that you believe it best documents the command and the way you would like to see it. Here are some of our ideas of documentation we would love to see (feel free to add yours):

Examples of using the command (max creativity welcomed!)
Description of the command.
Command usage.

Anything else?

Of course! (These are drafts) so feel free to leave feedback and suggestions in the same file.

Happy Documenting.