You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the website calls read-write tokens "Publish" tokens... if we want to keep this verbiage, feel free to adjust the values noted above accordingly (there may be reasons we want to push forward with read-write though... as it's a standard across GitHub & may more clearly communicate the capabilities of the permissions that token is associated with - ref. https://docs.npmjs.com/creating-and-viewing-access-tokens#creating-tokens-with-the-cli)
Summary
The CLI should support automation tokens (which are already available on the website)
Exit Criteria
npm token create
supports a new--token-type
flagread-write
, other values areread
&automation
--read-only
flag should map to--token-type=read
npm token list
outputs the corresponding token type (no longer just the "read-only" boolean)Examples
Potential Bikeshedding
read-write
tokens"Publish"
tokens... if we want to keep this verbiage, feel free to adjust the values noted above accordingly (there may be reasons we want to push forward withread-write
though... as it's a standard across GitHub & may more clearly communicate the capabilities of the permissions that token is associated with - ref. https://docs.npmjs.com/creating-and-viewing-access-tokens#creating-tokens-with-the-cli)References
https://www.npmjs.com/settings/<tokens>/tokens
The text was updated successfully, but these errors were encountered: