Support for Gitea / other Git forges?

Open
#5 2 comments 12 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
git, github, gitlab
Domain
developer-experience, devops

Research direction

Start by tracing how lapdev currently requires GitHub and GitLab repository sources, then determine the intended scope for Gitea or other forges. This issue mentions no files or tests, so first map the existing source integration and clarify which forge and repository operations must be supported. Done means an alternative forge can be used without requiring GitHub or GitLab.

Written by the indexing model from the issue text.

Description

I’m interested in using lapdev however, I’ve migrated my current projects off of Github and Gitlab. I want to use this project, however, I can’t due to the required Github/Gitlab sources of repos. Would it be possible for other forges to be used to prevent lockin?

Dominant language
Rust
Stars
2k
Forks
58
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lapce/lapdev

All issues in lapce/lapdev

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.