The user only has access to the fork, which likely contains the same commits
that his local clone does. He won't have access to anything new you push to
your repo. We may change collab revocation to remove the fork in the
future.
Tekkub
GitHub Tech Support
http://support.github.com/
Join us on IRC: #github on freenode.net
Discussion group: [email protected]
On Tue, Feb 16, 2010 at 5:24 PM, Swapnil <[email protected]> wrote:
> Hi Guys,
>
> We are trying to use GitHub for private repos and had a question.
> Consider the case where we added 3 users as collaborators for our
> private repo. One of them forks it. Later this person leaves the
> company so we revoke his account from our repo. However, he still has
> a forked repo which he continues to have access to.
>
> Isn't this a security concern for private repos? Is it possible to dis-
> allow forking or atleast delete forks for a user when we revoke
> access?
>
> Thanks
> Swapnil
>
> --
> You received this message because you are subscribed to the Google Groups
> "GitHub" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<github%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/github?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"GitHub" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/github?hl=en.
