feat: implement advanced pull request operations #6
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
Beyond basic PR CRUD, reviewers need to be requested explicitly, individual file
reviews differ from overall PR reviews, and review dismissals are used when a
review is outdated. These are standard code review workflow primitives.
Endpoints to implement
/repos/{owner}/{repo}/pulls/{index}/requested_reviewerslist_requested_reviewers/repos/{owner}/{repo}/pulls/{index}/requested_reviewersrequest_reviewers/repos/{owner}/{repo}/pulls/{index}/requested_reviewersremove_requested_reviewers/repos/{owner}/{repo}/pulls/{index}/fileslist_pr_files/repos/{owner}/{repo}/pulls/{index}/commitslist_pr_commits/repos/{owner}/{repo}/pulls/{index}/reviews/{id}get_pr_review/repos/{owner}/{repo}/pulls/{index}/reviews/{id}delete_pr_review/repos/{owner}/{repo}/pulls/{index}/reviews/{id}/dismissalsdismiss_pr_review/repos/{owner}/{repo}/pulls/{index}/reviews/{id}/dismissalsundismiss_pr_reviewAcceptance Criteria
request_reviewers(owner, repo, index, reviewers, team_reviewers)— both are optional listslist_pr_filesreturns list of changed files withfilename,status,additions,deletionslist_pr_commitsreturns commits in chronological orderdismiss_pr_review(owner, repo, index, id, message)requires a dismissal messagedelete_pr_reviewonly works onPENDINGreviews; document this constraint in docstringTechnical Notes
request_reviewersbody:{"reviewers": ["alice", "bob"], "team_reviewers": ["core-team"]}dismiss_pr_reviewbody:{"message": "Superseded by newer commit"}— message is required by Gitea APIAPPROVEDorREQUEST_CHANGESstate