-
-
Notifications
You must be signed in to change notification settings - Fork 958
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Gitea Pull Requests #7099
Comments
This issue has been added to the backlog. It is not scheduled on the Weblate roadmap, but it eventually might be implemented. In case you need this feature soon, please consider helping or push it by funding the development. |
Here's the documentation for the HTTP API of Gitea: https://try.gitea.io/api/swagger |
Historically, the implementation was done this way. The reason is that you need to change the VCS behavior to integrate with the code hosting site (for example, push to fork instead of pushing to original repo). The API URL is generated from the VCS URL: Lines 698 to 732 in 833ead3
It is customized per code hosting site: Lines 839 to 846 in 833ead3
The credentials are stored in the settings GITHUB_CREDENTIALS / GITLAB_CREDENTIALS / PAGURE_CREDENTIALS. |
Add Gitea VCS backend similar to GitHub and GitLab. Fixes WeblateOrg#7099 Supersedes WeblateOrg#7326 Co-authored-by: Michal Čihař <michal@cihar.com>
Thank you for your report; the issue you have reported has just been fixed.
|
Describe the problem
Pull requests are currently only supported against GitHub and GitLab, we'd like to use them against Gitea instead.
Describe the solution you'd like
Add support fir Gitea pull requests.
Here's the API documentation: https://try.gitea.io/api/swagger#/repository/repoCreatePullRequest
Describe alternatives you've considered
No response
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: