{"action":"opened","issue":{"url":"https://api.github.com/repos/ScazLab/ScazLab.github.io/issues/1","repository_url":"https://api.github.com/repos/ScazLab/ScazLab.github.io","labels_url":"https://api.github.com/repos/ScazLab/ScazLab.github.io/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/ScazLab/ScazLab.github.io/issues/1/comments","events_url":"https://api.github.com/repos/ScazLab/ScazLab.github.io/issues/1/events","html_url":"https://github.com/ScazLab/ScazLab.github.io/issues/1","id":193912575,"number":1,"title":"Change default repository permissions (was: write; will be: read)","user":{"login":"alecive","id":4378663,"avatar_url":"https://avatars.githubusercontent.com/u/4378663?v=3","gravatar_id":"","url":"https://api.github.com/users/alecive","html_url":"https://github.com/alecive","followers_url":"https://api.github.com/users/alecive/followers","following_url":"https://api.github.com/users/alecive/following{/other_user}","gists_url":"https://api.github.com/users/alecive/gists{/gist_id}","starred_url":"https://api.github.com/users/alecive/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/alecive/subscriptions","organizations_url":"https://api.github.com/users/alecive/orgs","repos_url":"https://api.github.com/users/alecive/repos","events_url":"https://api.github.com/users/alecive/events{/privacy}","received_events_url":"https://api.github.com/users/alecive/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-12-06T23:10:36Z","updated_at":"2016-12-06T23:10:36Z","closed_at":null,"body":"@ScazLab/scazlab_admins I'm writing here because we don't have a general way to create general issues that don't deal with a specific repo.\r\n\r\nI would like to change the default repository permissions for the generic ScazLab member from write to **read**. This means that members will be able to clone and pull all repositories, but not to push to any repository by default.\r\n\r\nThis has the big advantage of **automatically avoiding somebody inadvertently messing up with your repository**. To make things clearer, here is my use case (that is also the reason for which I would like to do this): I am currently having three students working on various aspect of the baxter_collaboration repo, which is great but is also at risk of lowering the level of the code (and increasing the risk of errors, and so on) because of these different contributions. Hence, I would like to _protect_ the `master` branch (i.e. the one I work on) to avoid anybody but the @ScazLab/scazlab_admins to be able commit to that branch. Any collaborator would be **forced** to open branches and pull request every time they need to push to master. I find it very clean and neat, but to do that I need this change in default permission settings. Btw more info on protected branches is [here](https://help.github.com/articles/about-protected-branches/) (they're pretty cool).\r\n\r\nThe biggest disadvantage is that some of your students may need to be granted access to the repos they are working on because they cannot push to it any more. You can do that in two ways:\r\n 1. Add them as collaborators of your repository, that is one-by-one\r\n 2. Add them in your scazlab team (see #2) and then grant write access to your team in your repo (that is, you do this once and you will never do it again).\r\n\r\nSo, to make it short, in order to do that I need you to be aware than when I'll do it you'll have some issues that will be easy to fix but can nonetheless be annoying. For this reason, I will do it only if everyone in the @ScazLab/scazlab_admins will give me his/her aye. @katemtsui @LarissaScazlab I think you have more important things to do than dealing with my security problems, so feel free to ignore this . For everyone else, I'll ping you one by one until everybody has answered :)"}}
{"actor":{"display_login":"alecive"}}