fork/cargo
git clone https://git.julia.blue/fork/cargo
1ce01c5e5
0.92.0
1CARGO-OWNER(1) 2 3NAME 4 cargo-owner — Manage the owners of a crate on the registry 5 6SYNOPSIS 7 cargo owner [options] --add login [crate] 8 cargo owner [options] --remove login [crate] 9 cargo owner [options] --list [crate] 10 11DESCRIPTION 12 This command will modify the owners for a crate on the registry. Owners 13 of a crate can upload new versions and yank old versions. Non-team 14 owners can also modify the set of owners, so take care! 15 16 This command requires you to be authenticated with either the --token 17 option or using cargo-login(1). 18 19 If the crate name is not specified, it will use the package name from 20 the current directory. 21 22 See the reference 23 <https://doc.rust-lang.org/cargo/reference/publishing.html#cargo-owner> 24 for more information about owners and publishing. 25 26OPTIONS 27 Owner Options 28 -a, --add login… 29 Invite the given user or team as an owner. 30 31 -r, --remove login… 32 Remove the given user or team as an owner. 33 34 -l, --list 35 List owners of a crate. 36 37 --token token 38 API token to use when authenticating. This overrides the token 39 stored in the credentials file (which is created by cargo-login(1)). 40 41 Cargo config <https://doc.rust-lang.org/cargo/reference/config.html> 42 environment variables can be used to override the tokens stored in 43 the credentials file. The token for crates.io may be specified with 44 the CARGO_REGISTRY_TOKEN environment variable. Tokens for other 45 registries may be specified with environment variables of the form 46 CARGO_REGISTRIES_NAME_TOKEN where NAME is the name of the registry 47 in all capital letters. 48 49 --index index 50 The URL of the registry index to use. 51 52 --registry registry 53 Name of the registry to use. Registry names are defined in Cargo 54 config files 55 <https://doc.rust-lang.org/cargo/reference/config.html>. If not 56 specified, the default registry is used, which is defined by the 57 registry.default config key which defaults to crates-io. 58 59 Display Options 60 -v, --verbose 61 Use verbose output. May be specified twice for “very verbose” 62 output which includes extra output such as dependency warnings and 63 build script output. May also be specified with the term.verbose 64 config value 65 <https://doc.rust-lang.org/cargo/reference/config.html>. 66 67 -q, --quiet 68 Do not print cargo log messages. May also be specified with the 69 term.quiet config value 70 <https://doc.rust-lang.org/cargo/reference/config.html>. 71 72 --color when 73 Control when colored output is used. Valid values: 74 75 o auto (default): Automatically detect if color support is 76 available on the terminal. 77 78 o always: Always display colors. 79 80 o never: Never display colors. 81 82 May also be specified with the term.color config value 83 <https://doc.rust-lang.org/cargo/reference/config.html>. 84 85 Common Options 86 +toolchain 87 If Cargo has been installed with rustup, and the first argument to 88 cargo begins with +, it will be interpreted as a rustup toolchain 89 name (such as +stable or +nightly). See the rustup documentation 90 <https://rust-lang.github.io/rustup/overrides.html> for more 91 information about how toolchain overrides work. 92 93 --config KEY=VALUE or PATH 94 Overrides a Cargo configuration value. The argument should be in 95 TOML syntax of KEY=VALUE, or provided as a path to an extra 96 configuration file. This flag may be specified multiple times. See 97 the command-line overrides section 98 <https://doc.rust-lang.org/cargo/reference/config.html#command-line-overrides> 99 for more information. 100 101 -C PATH 102 Changes the current working directory before executing any specified 103 operations. This affects things like where cargo looks by default 104 for the project manifest (Cargo.toml), as well as the directories 105 searched for discovering .cargo/config.toml, for example. This 106 option must appear before the command name, for example cargo -C 107 path/to/my-project build. 108 109 This option is only available on the nightly channel 110 <https://doc.rust-lang.org/book/appendix-07-nightly-rust.html> and 111 requires the -Z unstable-options flag to enable (see #10098 112 <https://github.com/rust-lang/cargo/issues/10098>). 113 114 -h, --help 115 Prints help information. 116 117 -Z flag 118 Unstable (nightly-only) flags to Cargo. Run cargo -Z help for 119 details. 120 121ENVIRONMENT 122 See the reference 123 <https://doc.rust-lang.org/cargo/reference/environment-variables.html> 124 for details on environment variables that Cargo reads. 125 126EXIT STATUS 127 o 0: Cargo succeeded. 128 129 o 101: Cargo failed to complete. 130 131EXAMPLES 132 1. List owners of a package: 133 134 cargo owner --list foo 135 136 2. Invite an owner to a package: 137 138 cargo owner --add username foo 139 140 3. Remove an owner from a package: 141 142 cargo owner --remove username foo 143 144SEE ALSO 145 cargo(1), cargo-login(1), cargo-publish(1) 146