-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
API repos search should return private repos of that user #6183
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
Comments
Isn't that fixed by #5383 ? |
No, unless I am missing something. I am testing on latest master (v1.7.0-dev-241-g594f59169). I guess it only fixed it for |
I can confirm that this is still an issue and affects the organisation view on the dashboard. |
@zeripath Could you clarify how it affects the organisation view on the dashboard? I had a look but couldn't find anything wrong there. |
OK, log in as [email protected] with the same password on to http://try.gitea.io arandomer2 has read access to TestOrgAnother, although TestOrgAnother/private-test-repository appears on arandomer2 dashboard take a look at: |
Ah I see. |
It's supposed to give you the newsfeed for that organisation context. The + repository button would allow you to create a repository in that organisation by default if you're allowed to create repositories for that organisation. |
I don't think you're supposed to see the organisation repos in the right hand box unless you're in the organisation context either |
I think this is finally fixed by #6897 in 1.9 |
Description
Hello and thank you very much for your work on gitea!
I think that similarily to #5310,
GET /repos/search
should return the private repos that the logged in user has access to. Currently only when you adduid=$CURRENT_USER_ID
can you see the private repos (but then you don't see other people repos).Changing this would make it behave more like the current
/explore/repos
non-api endpoint.The text was updated successfully, but these errors were encountered: