-
Suggestion
-
Resolution: Answered
-
None
-
None
This suggestion is to make the "path" parameter optional for the function http://example.com/rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/pull-requests/{pullRequestId}/comments, since general comments on pull requests aren't anchored to a path, thus you can't get them using this function - currently it's only possible to get comments from files using it.
If you try not setting the "path", the return is:
{"errors":[{"context":null,"message":"The path query parameter is required when retrieving comments.","exceptionName":null}]}
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[BSERV-7643] Make "path" optional for the pull requests comments REST API function
gyerts2114728143 - see this answer https://answers.atlassian.com/questions/21634693/answers/21634860
I think the activity API is the right approach for getting this information.
We within our enterprise use Bitbucket server on-premise. We are keen to implement a Gitops style process on how we merge pull-requests. So it would be really helpful to get comments on the pull-request itself.
the comments can be commands/instructions very similar to prow project in kubernetes/test-infra.
So, need to fetch comments at PR (instead of paths) would help.