Trigger a Weblate reset after pushing translations #5347
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
After we have told Weblate to push all of its pending commits, it should forget about them. The reason is that we may revert some code samples, and when the translations PR finally squash-merges its way onto `main` and gets back to Weblate, it will see a conflict with its own pending changes. By resetting, it will forget about its own pending changes, and think we are just great upstream translators!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After we have told Weblate to push all of its pending commits, it should forget about them.
The reason is that we may revert some code samples, and when the translations PR finally squash-merges its way onto
mainand gets back to Weblate, it will see a conflict with its own pending changes.By resetting, it will forget about its own pending changes, and consume the changes when they finally come in from the upstream repo.
This probably leads to an inconsistency window in which it looks for about ~1hr like the changes have disappeared. Fear not, they haven't, they will come back once the PR is in and Weblate syncs from the main repo.