Codeberg/Community
54
325
Fork
You've already forked Community
12

Pushing changes from Weblate via GitHub pull requests #1630

Closed
opened 2024年08月12日 02:33:26 +02:00 by DogmaDragon · 10 comments

Comment

Weblate https://docs.weblate.org/en/latest/admin/continuous.html#push-changes indicate that GitHub pull requests are supported, but https://docs.codeberg.org/codeberg-translate/getting-started/ only mentions Gitea as an option for pull requests.

Is there a way to automate translations via pull requests from Codeberg Translate to GitHub?

### Comment Weblate https://docs.weblate.org/en/latest/admin/continuous.html#push-changes indicate that GitHub pull requests are supported, but https://docs.codeberg.org/codeberg-translate/getting-started/ only mentions Gitea as an option for pull requests. Is there a way to automate translations via pull requests from Codeberg Translate to GitHub?

but https://docs.codeberg.org/codeberg-translate/getting-started/ only mentions Gitea as an option for pull requests

This documentation page assumes your repository is also on Codeberg. If you're using a Github repository, it should give you the option to use Github pull requests.

> but https://docs.codeberg.org/codeberg-translate/getting-started/ only mentions Gitea as an option for pull requests This documentation page assumes your repository is also on Codeberg. If you're using a Github repository, it should give you the option to use Github pull requests.

There is no such option under VCS. Are there some prerequisites that need to be done to enable it?
image

There is no such option under VCS. Are there some prerequisites that need to be done to enable it? ![image](/attachments/6c00d899-ee0a-417d-b98f-9c0f9b58bd2d)

Ah sorry, I just checked but Github isn't supported on translate.codeberg.org, it's only available for projects on Codeberg.org

Ah sorry, I just checked but Github isn't supported on translate.codeberg.org, it's only available for projects on Codeberg.org

I see. Could you share the rationale behind the artificial limitation, since Weblate supports it natively?

I see. Could you share the rationale behind the artificial limitation, since Weblate supports it natively?
Owner
Copy link

It is not artificially limited, I think it is just not set up. So it would require someone actually configuring it to connect to GitHub, as far as I understand it (creating an account at GitHub to be used by Codeberg Translate).

We did this for GitLab, because a project wanted to use it, but I believe it would require more discussion whether this is in scope for Codeberg. Obviously, it is not our primary goal to offer convenience features for GitHub.

Is there a specific reason you want to use Codeberg Translate together with GitHub? Why not the official Weblate hosting?

It is not artificially limited, I think it is just not set up. So it would require someone actually configuring it to connect to GitHub, as far as I understand it (creating an account at GitHub to be used by Codeberg Translate). We did this for GitLab, because a project wanted to use it, but I believe it would require more discussion whether this is in scope for Codeberg. Obviously, it is not our primary goal to offer convenience features for GitHub. Is there a specific reason you want to use Codeberg Translate together with GitHub? Why not the official Weblate hosting?
Owner
Copy link

Correcting: We didn't set up GitLab pull requests, but we configured pushing to GitLab via a special user.

Correcting: We didn't set up GitLab pull requests, but we configured pushing to GitLab via a special user.

We did this for GitLab, because a project wanted to use it, but I believe it would require more discussion whether this is in scope for Codeberg. Obviously, it is not our primary goal to offer convenience features for GitHub.

Are we really sure that we don't want to help people mix-and-match whatever they feel like is appropriate for their use case and that motivating people to reduce their dependency on GitHub's infrastructure by reducing the amount of GitHub-provided offerings they use to begin with (thus making a possible future migration onto another platform like ours or a self-hosted instance) is not in line with our goals?

All translators using Codeberg Translate would have to create Codeberg accounts, so I'd imagine that open-source projects that are considering to switch could benefit from this so as to reduce the "but all of our contributors are on GitHub" factor.

It's OK if this is not a priority.

> We did this for GitLab, because a project wanted to use it, but I believe it would require more discussion whether this is in scope for Codeberg. Obviously, it is not our primary goal to offer convenience features for GitHub. Are we really sure that we don't want to help people mix-and-match whatever they feel like is appropriate for their use case and that motivating people to reduce their dependency on GitHub's infrastructure by reducing the amount of GitHub-provided offerings they use to begin with (thus making a possible future migration onto another platform like ours or a self-hosted instance) is not in line with our goals? All translators using Codeberg Translate would have to create Codeberg accounts, so I'd imagine that open-source projects that are considering to switch could benefit from this so as to reduce the "but all of our contributors are on GitHub" factor. It's OK if this is not a priority.

Is there a specific reason you want to use Codeberg Translate together with GitHub? Why not the official Weblate hosting?

We used to self-host our own Weblate instance, but maintenance was stretching limited resources. So we tried applying to Weblate Libre plan, but it was rejected for being a bad fit due to the adult nature of the project.

> Is there a specific reason you want to use Codeberg Translate together with GitHub? Why not the official Weblate hosting? We used to self-host our own Weblate instance, but maintenance was stretching limited resources. So we tried applying to Weblate Libre plan, but it was rejected for being a bad fit due to the adult nature of the project.

Second person wanting to use Codeberg Translate with GitHub here.
Similar story to DogmaDragon, we are self-hosting our own instance right now, but there are several downsides to that. Hosted Weblate is too limiting compared to Codeberg Translate.

What is probably worth mentioning is that Codeberg should probably create a GitHub user, even if GitHub isn't supported, because someone else can create a GitHub user for Codeberg without asking.
This also means that I can take care of creating said user for GitHub. I could also create one, clearly state that it is unofficial, and leave my contact details in case Codeberg wants me to remove it or do something with it.
I can also help someone else set it up, though it is pretty easy if you understand what you are doing.

Second person wanting to use Codeberg Translate with GitHub here. Similar story to DogmaDragon, we are self-hosting our own instance right now, but there are several downsides to that. Hosted Weblate is too limiting compared to Codeberg Translate. What is probably worth mentioning is that Codeberg should probably create a GitHub user, even if GitHub isn't supported, because someone else can create a GitHub user for Codeberg without asking. This also means that I can take care of creating said user for GitHub. I could also create one, clearly state that it is unofficial, and leave my contact details in case Codeberg wants me to remove it or do something with it. I can also help someone else set it up, though it is pretty easy if you understand what you are doing.

There is now a GitHub account set up for pushing changes from Codeberg Translate to GitHub.
You use it like any other Weblate GitHub account, but just in case I put instructions on its profile. https://github.com/Codeberg-Translate
With this, I believe we can close this issue.

There is now a GitHub account set up for pushing changes from Codeberg Translate to GitHub. You use it like any other Weblate GitHub account, but just in case I put instructions on its profile. https://github.com/Codeberg-Translate With this, I believe we can close this issue.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
5 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#1630
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?