-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Collaborators in repositories in private organisations cannot access repository #6962
Closed
3 of 7 tasks
Labels
Comments
This seems to be from @lunny PR #6743 gitea/models/repo_permission.go Lines 171 to 174 in 7dd9837
Maybe there needs to be a check here if they are a collaborator (similar as below) and set access perms/not return if so? |
mrsdizzie
added a commit
to mrsdizzie/gitea
that referenced
this issue
May 16, 2019
Handle case where an orginization is private but a user who is not a member of the orgninization has been added as a collaborator of a repo within that org Fixes go-gitea#6962
techknowlogick
pushed a commit
that referenced
this issue
May 16, 2019
Handle case where an orginization is private but a user who is not a member of the orgninization has been added as a collaborator of a repo within that org Fixes #6962
mrsdizzie
added a commit
to mrsdizzie/gitea
that referenced
this issue
May 16, 2019
Handle case where an orginization is private but a user who is not a member of the orgninization has been added as a collaborator of a repo within that org Fixes go-gitea#6962
jeffliu27
pushed a commit
to jeffliu27/gitea
that referenced
this issue
Jul 18, 2019
Handle case where an orginization is private but a user who is not a member of the orgninization has been added as a collaborator of a repo within that org Fixes go-gitea#6962
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
[x]
):Description
If I create a repository in a private organization and add a collaborator who is not a member of that organization they cannot access the repository despite it being it appearing on their dashboard.
Screenshots
The text was updated successfully, but these errors were encountered: