Provider a HTTP server as a proxy to communicate with Gitlab/GitHub
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 18
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Why
It would be good to have a unified HTTP API to communicate with Gitlab/GitHub. So other tools don't need to consider the details.
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are identified in the issue. Start by reviewing the repository's Go entry points and existing Git provider communication, then define the unified HTTP API boundary. Done means other tools can communicate with GitLab and GitHub through the proxy without handling provider-specific details.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100