Skip to content

feat(provider): add Gitea support (#2904)#13127

Closed
yemsy26 wants to merge 2 commits intogitbutlerapp:masterfrom
yemsy26:feat/gitea-provider-support-2904
Closed

feat(provider): add Gitea support (#2904)#13127
yemsy26 wants to merge 2 commits intogitbutlerapp:masterfrom
yemsy26:feat/gitea-provider-support-2904

Conversation

@yemsy26
Copy link
Copy Markdown

@yemsy26 yemsy26 commented Mar 31, 2026

Summary

Implemented full support for Gitea as a code hosting provider.

  • Added but-gitea crate with API client and PR operations
  • Support self-hosted instances via configurable base URL
  • Integrated storage, forge dispatch, API exposure, and generated TS bindings

Fixes #2904
/claim #2904

- Implement but-gitea crate mirroring but-github/but-gitlab patterns
- Add PAT and self-hosted Gitea account storage in but-forge-storage
- Integrate Gitea into but-forge (host detection, account listing, review ops)
- Expose Gitea auth commands via but-api and Tauri
- Generate and export ButGitea/ButGiteaToken TypeScript bindings
- Enable Gitea as first-class forge provider alongside GitHub/GitLab

Fixes: gitbutlerapp#2904
@vercel
Copy link
Copy Markdown

vercel bot commented Mar 31, 2026

@yemsy26-create is attempting to deploy a commit to the GitButler Team on Vercel.

A member of the Team first needs to authorize it.

@yemsy26
Copy link
Copy Markdown
Author

yemsy26 commented Mar 31, 2026

I've implemented the Gitea provider support in a new modular crate but-gitea and updated the bindings for the frontend. Ready for review and deployment authorization. /claim #2904

@Byron
Copy link
Copy Markdown
Collaborator

Byron commented Apr 8, 2026

I'm sorry to say this, but I don't think we have the capacity right now to review any Gitea related PRs.

To have a chance to get something like that merged you'd find a sponsor within the team first that will be willing to review it. And to do that they would have to know you perform the validation necessary and gain trust in your willingness deliver quality work.

Thus I recommend starting with an issue where you layout your plan to implement this and more importantly to validate it. And maybe from there a PR can happen.

Thanks for your understanding.

@Byron Byron closed this Apr 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Gitea support

3 participants