Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move to npm team #1

Open
pascalduez opened this issue Nov 11, 2015 · 5 comments
Open

Move to npm team #1

pascalduez opened this issue Nov 11, 2015 · 5 comments

Comments

@pascalduez
Copy link
Member

https://docs.npmjs.com/cli/team

@valeriangalliat
Copy link
Member

I was about to say "sweeeet!" but I see it's not used to handle package permissions? So what would we use it for?

@pascalduez
Copy link
Member Author

Humm, not so clear indeed, something to do with organizations I guess, might imply a scope.
https://docs.npmjs.com/getting-started/working-with-orgs

Looks like the way to manage permissions is using the access command:
https://docs.npmjs.com/cli/access

npm access grant <read-only|read-write> <scope:team> [<package>]

@valeriangalliat
Copy link
Member

Oh so we can give access to a package through a team? Like all SassDoc packages belongs to SassDoc team, and anybody joining the team would have automatically access too? And any new package would be granted to all the team? Would be great.

@valeriangalliat
Copy link
Member

@pascalduez I can't create a team, at least not on the public repository, I get a 401 for npm team create developers:sassdoc. I believe it's something dedicated to private registries?

EDIT: oh we need to create the org first... gonna try.

@valeriangalliat
Copy link
Member

Okay I've requested access, I'll recieve a mail if we're granted to try the teams feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants