Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

access #3

Closed
ghost opened this issue Aug 29, 2017 · 2 comments
Closed

access #3

ghost opened this issue Aug 29, 2017 · 2 comments

Comments

@ghost
Copy link

ghost commented Aug 29, 2017

I went through the list of maintainers for browserify core and related repos and added everyone as an owner. This way everybody has access to all org repos and can add more people.

I would like to do the same for all the npm packages I am a maintainer on so that anybody can cut a new release on npm as well as github. Maybe we could have a file with both github and npm user names for everybody in the org? And when a new user is added, the person who added them can add their npm and github user names to that file. Where should that file live?

@gkatsev
Copy link

gkatsev commented Aug 29, 2017

npm orgs might be useful for managing the npm access since all the packages can be added to the org and a team and then a user only needs to be added once to have access to everything in the team.

While the docs for it don't say so, you can add public packages to it with something like

npm access grant read-write browserify:developers node-browserify

Though, npm has a bug currently where depending on permissions of users that are on the package, you might need to go through npm support for it until it gets fixed.

@ghost
Copy link
Author

ghost commented Aug 29, 2017

Great, I've added the packages I control to the org and added everybody as an owner so that anybody can add more people.

@ghost ghost closed this as completed Aug 29, 2017
@browserify browserify locked and limited conversation to collaborators Nov 22, 2023
@balupton balupton converted this issue into discussion #17 Nov 22, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant