-
Notifications
You must be signed in to change notification settings - Fork 0
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
Reorganizing teams #7
Comments
👍 |
Approve. |
👍 If you want to create a repo, you'd have to proxy the request to an admin. Which makes sense? |
Oh hmm… I'll need to look into that. I'd hate to stall people by preventing them from creating repos. Mostly I just want to restrict access to admin login type data to only the people that need it. |
Yeah, and the same goes for editing existing public repos. You'd have to fork it to your personal account and send a PR |
Hmm that sucks. Alright, let me see if I can figure out a better solution. |
How does GitHub even work? Ok, I think I've got it set up so people in @CoderDojoSF/mentors should be able to create repos. If you aren't able to, let me know. |
Yup, @CoderDojoSF/mentors can now create repos but, they don't have access to public repos |
Wat? @KartikTalwar so you can create repos but you can't push/pull to existing repos? |
@cameronmcefee yeah, because the mentors team is restricted to mentor-tickets repo |
Ugh, right. Ok, let me fix that too. If you create a new repo, do only you get access to it, or do all mentors, I wonder. |
I believe all team members with push and pull access do.
|
Alright, all the repos are part of the mentors team now. Sorry if you got notifications for each of them. Hopefully this resolves things. If not, give me a shout and I'll see if we can improve the process further. |
cc @CoderDojoSF/owners @CoderDojoSF/mentors
I'd like to do some restructuring of this org's teams to optimize our permission stuff a bit so that more people can be involved in the admin processes.
In an effort to keep things moving along, I'm going to make these changes now. If there are any concerns regarding this issue, we can address them as they come.
The text was updated successfully, but these errors were encountered: