APIs for pull requests
Open
Nobody has claimed this yet.
🎯 feature
status: assigned to community
- Dominant language
- Go
- Stars
- 47.8k
- Forks
- 5.1k
- Avg merge
- 7h 23m
- Merged PRs (30d)
- 5
Description
Particularly these commands are desired:
- /api/v1/{user}/{repo}/pulls?status={open/closed}&id={id} - retrieves the list of pull requests (or one pull request)
- /api/v1/{user}/{repo}/pull/{num}/files - retrieves the list of affected files for the pull request
- /api/v1/{user}/{repo}/pull/{num}/diff - retrieves the diff file for the pull request
- /api/v1/{user}/{repo}/pull/{num}/comments - retrieves the list of comments
- /api/v1/{user}/{repo}/pull/{num}/comment-submit - PUT submits a new comment
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the requested /api/v1/{user}/{repo}/pulls and /pull/{num}/... endpoint paths, then inspect the repository's existing API conventions and pull-request model. Confirm behavior for status filtering, single-ID lookup, files, diffs, comments, and PUT comment submission, with coverage for each route.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100