WeblateOrg / weblate

Web based localization tool with tight version control integration.
https://weblate.org/
GNU General Public License v3.0
4.61k stars 1.02k forks source link

Translation files commited in wrong path #5976

Closed Deuchnord closed 3 years ago

Deuchnord commented 3 years ago

Hello,

Describe the issue I am configuring a new project on the hosted Weblate instance, and I am having a weird issue, where the Github integration keeps committing files in the wrong path: as you can see in this PR: https://github.com/Kosmorro/kosmorro/pull/175, the app is creating files in /kosmorrolib/locales/{lang}.po.

I already tried

Describe the steps you tried to solve the problem yourself.

Expected behavior

Files should be created in kosmorrolib/locales/*/LC_MESSAGES/messages.po.

Server configuration and status

Weblate installation: weblate.org service

Additional context

Before having this filemask value, I had the wrong kosmorrolib/locales/*.po configuration value, so this may be related.

github-actions[bot] commented 3 years ago

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!

nijel commented 3 years ago

If the files were created with that filemask, it behaves as expected. Weblate doesn't change the history once the files are comitted to the Git repostory.

Deuchnord commented 3 years ago

Thanks for your answer. I understand that, but how then, how do I tell Weblate to remove those files from its repository?

nijel commented 3 years ago

You can do any changes in the upstream repository and reset Weblate one to match it.

Deuchnord commented 3 years ago

Just reset the commit history on Weblate, looks like the issue is now solved (doesn't repeat creating PRs anymore). Closing this issue, thanks for your help @nijel :)

github-actions[bot] commented 3 years ago

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.