Not that important for now, but will have to do this sooner or later, the idea is to namespace organizations separately by giving them a + prefix but treating them quite similar to users. Permissions should apply to every repo an organization owns (don't see much value in making this more complicated, if one requires separate permissions per project then just make multiple organizations). It'd also be nice if organizations could have SSH keys so that a server could gain access to private repos by putting their public key in the organizations authorized_keys, really dislike how I had to create special accounts for servers (although I think GH now has support for deploy keys, think I used that once).
Not that important for now, but will have to do this sooner or later, the idea is to namespace organizations separately by giving them a + prefix but treating them quite similar to users. Permissions should apply to every repo an organization owns (don't see much value in making this more complicated, if one requires separate permissions per project then just make multiple organizations). It'd also be nice if organizations could have SSH keys so that a server could gain access to private repos by putting their public key in the organizations authorized_keys, really dislike how I had to create special accounts for servers (although I think GH now has support for deploy keys, think I used that once).
Not yet