{"action":"opened","issue":{"url":"https://api.github.com/repos/jennybc/happy-git-with-r/issues/39","repository_url":"https://api.github.com/repos/jennybc/happy-git-with-r","labels_url":"https://api.github.com/repos/jennybc/happy-git-with-r/issues/39/labels{/name}","comments_url":"https://api.github.com/repos/jennybc/happy-git-with-r/issues/39/comments","events_url":"https://api.github.com/repos/jennybc/happy-git-with-r/issues/39/events","html_url":"https://github.com/jennybc/happy-git-with-r/issues/39","id":178619831,"number":39,"title":"Notes for GitHub use in classroom","user":{"login":"jennybc","id":599454,"avatar_url":"https://avatars.githubusercontent.com/u/599454?v=3","gravatar_id":"","url":"https://api.github.com/users/jennybc","html_url":"https://github.com/jennybc","followers_url":"https://api.github.com/users/jennybc/followers","following_url":"https://api.github.com/users/jennybc/following{/other_user}","gists_url":"https://api.github.com/users/jennybc/gists{/gist_id}","starred_url":"https://api.github.com/users/jennybc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jennybc/subscriptions","organizations_url":"https://api.github.com/users/jennybc/orgs","repos_url":"https://api.github.com/users/jennybc/repos","events_url":"https://api.github.com/users/jennybc/events{/privacy}","received_events_url":"https://api.github.com/users/jennybc/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-09-22T14:07:04Z","updated_at":"2016-09-22T14:07:04Z","closed_at":null,"body":"2016 outline (most of these requests have additional info in the body btw):\r\n\r\n  * get GitHub username via Shiny form app\r\n  * ping them to make sure exist `GET /users/:username`\r\n    - all did (!!) but some typos, of course, which were all valid usernames, which meant I invited randos to join the org at first (all straightened out now)\r\n  * create 2016_students name and store id `POST /orgs/STAT545-UBC/teams`\r\n  * invite students to join the team (and therefore org) `PUT /teams/:id/memberships/:username`\r\n  * create student-specific repos `POST /orgs/STAT545-UBC/repos`\r\n  * add student as collaborator `PUT /repos/STAT545-UBC/:repo/collaborators/:username`\r\n  * grant 2016_students team read access to all student repos `PUT /teams/:id/repos/STAT545-UBC/:repo`\r\n  * unwatch all the repos personally `DELETE /repos/:owner/:repo/subscription`\r\n  * iterate endlessly as students gradually register, fill out the form, etc.\r\n\r\nFirst year I have not created singleton teams and granted repo access solely through singleton team membership. In 2014 that was necessary due to restrictions in team/org permissions. By 2015 that had changed, but the change was very new and I didn't change my behaviour. 2016 is the first year I've taken advantage of fact you can add individuals as collabs to private Org-owned repos.\r\n\r\nAnd here's a peculiar consequence.\r\n\r\nStudents can start pushing their repos right away. Specifically, can do so w/o accepting the invitation to join the Org. You discover this when you try to assign them peer review. `POST /repos/:owner/:repo/issues` gives 422 whenever the putative reviewer (who will be specified as assignee in the body of the request) is not a member of the 2016_students team, which is what confers the necessary read access.\r\n"}}
{"actor":{"display_login":"jennybc"}}