"cargo owner --add" doesn't seem to work with teams

[sophiajt]

Problem

We've tried a few different ways of adding a team to grant the publishing rights to Nushell's repo, but haven't been able for this to work.

Here's what we're seeing:

〉 cargo owner --add github:nushell:publishing
error: failed to invite owners to crate `nu` on registry at https://crates.io

Caused by:
  the remote server responded with an error: could not find the github team nushell/publishing

The team does exist on github:

Steps

1. see above

Possible Solution(s)

It'd be nice to perhaps give a better error to help add a team if there's an issue with adding the specific team. Otherwise, I think this should work based on the name of the org + team.

Notes

No response

Version

cargo 1.66.0 (d65d197ad 2022-11-15)
release: 1.66.0
commit-hash: d65d197ad5c6c09234369f219f943e291d4f04b9
commit-date: 2022-11-15
host: aarch64-apple-darwin
libgit2: 1.5.0 (sys:0.15.0 vendored)
libcurl: 7.84.0 (sys:0.4.55+curl-7.83.1 system ssl:(SecureTransport) LibreSSL/3.3.6)
os: Mac OS 13.0.1 [64-bit]

[weihanglo]

Sorry about that. Looks like you hit this issue. Have you tried following that steps?

[sophiajt]

Yes, I think that ultimately was it. I had to revoke permissions, then have crates.io ask for them again after revoking them (log out then log back in, and then it asks), then make sure that nushell was in the grant for the permissions it asked for.

Something that would help a lot here is to show some screenshots of the github and crates.io side. I read through the text a bunch but it didn't click what exactly was meant since I kept seeing crates.io listed in the oauth apps that had permission. It was only after the 5th read it finally hit me that it was too old to have the proper permissions granted.

[VincentWo]

I could take over this issue if wanted :)

[weihanglo]

@VincentWo go ahead! I guess adding one or two screenshots as what JT said under this paragraph is sufficient. You may need an org account to reproduce the error.

[VincentWo]

Will do - thank you for the pointer.

But I wonder whether it would also be a goal to improve the error message

[weihanglo]

Oh yup. Nice suggestion! We could also provide a link to https://doc.rust-lang.org/cargo/reference/publishing.html#github-permissions in the error message.

[torhovland]

As discussed in #12511, I have opened a PR against crates.io here: rust-lang/crates.io#8593

[torhovland]

I am actually not sure if the documentation is wrong or incomplete. Somebody with a GitHub org account should try to first login with a key without the read:org scope, and then figure out what needs to be cleaned up in order to get things working.