Skip to content
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

Public content for authorized user #82

Open
jmgiaever opened this issue Oct 19, 2017 · 0 comments
Open

Public content for authorized user #82

jmgiaever opened this issue Oct 19, 2017 · 0 comments

Comments

@jmgiaever
Copy link

jmgiaever commented Oct 19, 2017

The documentation states that querying:

  • repositories GET {url}/api/v1/users/{username}/{repos}
  • organizations GET {url}/api/v1/users/{username}/{orgs}
  • etc
    should only return public data of that user. That isn't the fact if the {username} is the same user that owns the api-token, instead everything is returned.

This is what one can expect when issuing the GET {url}/api/v1/user/repos and similar requests for the authorized user.

Either must the documentation be changed to cover the differences or the code should actually return the public data within the scopes for public data.

Second one makes the most sense.... It would be convenient to actually have an method to get only public data, even for the authorized user, as the data returned for some requests (such as organizations) doesnt tell if this data is a private or public.

Gogs Version: 0.11.29.0727

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant