-
-
Notifications
You must be signed in to change notification settings - Fork 959
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
Weblate could not push changes to the upstream repository #7129
Comments
This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger. In case your question is already answered, making a donation is the right way to say thank you! |
The push to https without credentials could never work, so most likely some configuration was changed. Follow the hints in the alert to fix that. |
Thanks! For anyone who is still struggling: In the Settings for a component in Weblate, use this Repository push URL: Ex: Hopefully it works for you. |
Problem with this now is that it doesn't make a pull request, it just pushes them directly to the Repo. |
That is expected with "Git" as version control, you need "GitHub" for that. See https://docs.weblate.org/en/latest/admin/continuous.html#pushing-changes-from-weblate |
So there is no need for credentials if I selected |
The issue you have reported is now resolved. If you don’t feel it’s right, please follow its labels to get a clue for further steps.
|
Describe the issue
It was working fine yesterday. It's now unable to push to my Repo. I have authorization setup and everything working fine. The only think I may did in that time was resetting it in the Maintenance tab.
I already tried
Steps to reproduce the behavior
I don't know how
Expected behavior
To just push normally as yesterday.
Screenshots
Exception traceback
No response
How do you run Weblate?
weblate.org service
Weblate versions
No response
Weblate deploy checks
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: