Remove legacy localization automation#399
Merged
leandroalonso merged 1 commit intotrunkfrom Oct 31, 2022
Merged
Conversation
It was still part of the project because it had to be used to solve an issue during the previous release cycle.
Base automatically changed from
task/change-translation-tooling-for-next-code-freeze
to
trunk
October 17, 2022 11:38
Member
|
@mokagio I'll keep this open for now just in case we need to revert back to it (hopefully we won't need to do that). :) |
Contributor
Author
|
@leandroalonso @emilylaguna just checking how the 7.25 release cycle and 7.26 code freeze went and wether we can merge this 😄 |
leandroalonso
approved these changes
Oct 31, 2022
Member
|
@mokagio Merging it! |
leandroalonso
deleted the
mokagio/remove-legacy-translation-automation
branch
This was referenced Jan 27, 2023
Draft
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
It was still part of the project because it had to be used to solve an issue during the previous, 7.23 and 7.24, release cycles.