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

Get issue comments API didn't return review details #9345

Open
2 of 7 tasks
NepPure opened this issue Dec 13, 2019 · 4 comments
Open
2 of 7 tasks

Get issue comments API didn't return review details #9345

NepPure opened this issue Dec 13, 2019 · 4 comments
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/enhancement An improvement of existing functionality

Comments

@NepPure
Copy link

NepPure commented Dec 13, 2019

Description

Test PR https://try.gitea.io/oyyzowen/test2/pulls/5?lang=en-US

API:/repos/{owner}/{repo}/issues/{index}/comments don't work as expected.

Screenshots

image

image

@NepPure NepPure changed the title Get issue comments API didn't returns review details Get issue comments API didn't return review details Dec 13, 2019
@lunny lunny added the type/enhancement An improvement of existing functionality label Dec 13, 2019
@NepPure
Copy link
Author

NepPure commented Dec 17, 2019

Type: models.CommentTypeComment,

Include CommentTypeCode, add a new API, or add a parameter for comment type filtering?
Which solution would be better?

@lunny
Copy link
Member

lunny commented Dec 17, 2019

Maybe github could give use some idea.

@NepPure
Copy link
Author

NepPure commented Dec 17, 2019

https://developer.github.com/v3/pulls/comments/#list-comments-on-a-pull-request

Github has a separate set of APIs for pull request.
We can get review details from https://api.github.com/repos/go-gitea/gitea/pulls/9274/comments

@stale
Copy link

stale bot commented Feb 15, 2020

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale stale bot added the issue/stale label Feb 15, 2020
@lunny lunny added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Feb 16, 2020
@stale stale bot removed the issue/stale label Feb 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/enhancement An improvement of existing functionality
Projects
None yet
Development

No branches or pull requests

2 participants