Rust大闸蟹 088e662285
Replace git current_branch to shadow-rs branch (#2935)
* update to shadow-rs 0.4. use easy

* update shadow-rs to 0.5

* fix version not used

* update

* update Cargo.lock

* update Cargo.lock

* fix wasm build error when use dependence git2
fix error link:https://dev.azure.com/nushell/nushell/_build/results?buildId=4858&view=logs&j=1a745d4c-b027-5f34-06d8-d6f256bfe9f9&t=a0a335cb-fa1f-5bbf-be01-1a90d6899e54

* remove code not used; fix warning by RUSTFLAGS="-D warnings" build error

* upgrade shadow-rs 0.5.2

* upgrade shadow-rs 0.5.7

make nushell reduce dependence crates smaller and  build fast.

* upgrade shadow-rs 0.5.8

fix when use api 'strip_prefix()' method in less than rust1.45.0 build failed

* use shadow-rs branch replace with current_branch method;
remove and reduce git dependencies.

* upgrade shadow-rs 0.5.12-pre,test build error with wasm

* upgrade Cargo.lock

* upgarde shadow-rs depencdence

* fix build error in wasm

* add clippy warning
2021-01-16 07:06:29 +13:00
..
2021-01-13 14:46:15 +13:00
2020-06-28 14:22:26 +12:00
2019-10-08 18:32:42 +11:00
2020-07-23 09:42:04 +12:00
2020-08-15 07:52:59 -05:00
2021-01-15 20:21:18 +13:00
2020-10-06 05:21:20 -05:00
2021-01-02 17:24:32 +13:00
2020-09-30 13:27:52 -05:00
2020-03-14 06:23:41 +13:00
2020-12-16 05:37:12 +13:00
2020-09-07 17:02:45 +12:00
2020-06-28 14:22:26 +12:00
2020-12-09 06:43:46 +13:00
2020-05-24 02:02:44 -05:00
2020-08-22 05:51:29 +12:00
2020-07-15 08:47:04 +12:00
2020-10-15 16:20:55 +13:00
2020-10-15 16:20:55 +13:00
2021-01-02 17:24:32 +13:00
2020-10-01 20:13:42 -05:00

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.