Add API endpoints for pulls created by, assigned to and requested to review for a user

[MarkusAmshove]

Hi,

I wanted to create a tool to have a better overview of my pull requests (created), the ones I'm assigned to and the ones I've been requested to do a review.

I wanted to add the endpoints myself, but before doing any work, they should be designed and agreed upon :-)

Suggestion

I've chosen /api/.../pulls for this proposal, because this path is is the same the UI uses (e.g. https://gitea.com/pulls when logged in).

GET /api/v1/pulls: returns all pull requests from all repositories the authenticated user can see (same as with the UI).

GET /api/v1/pulls/created: returns all pull requests from all repositories the authenticated user has created

GET /api/v1/pulls/assigned: returns all pull requests from all repositories the authenticated user was assigned to

GET /api/v1/pulls/reviewee: returns all pull requests from all repositories the authenticated user was requested to do a review

If they're implemented, the filters in the UI could reuse them and also add a new filter (reviewee):

[stale]

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.

[6543]

@MarkusAmshove sorry for the late responce

what about add filter options in-query for GET /repos/issues/search docu

so issues can be filtered the same way ... yes name is bit missleading, but since pulls are "issues with additional info" it's handled that way ... (I think we should mention pulls in the endpoint description too ...)

[MarkusAmshove]

That would be fine :-)
If the query string from that endpoint can support all my usecases (even if that means multiple invocations) then I have all I need :-)

[6543]

closed by #13514