Repository navigation
Merge dev into next-dev - #41
Merged
Merged
Conversation
Updated translations from lokalise on Tue May 12 15:47:31 PDT 2026
Updated translations from lokalise on Fri Jun 26 12:54:46 PDT 2026
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
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.
Merges
mainintonext-devso that LoopKit/LoopWorkspace#454 (next-dev → dev) no longer conflicts and drops nothing from dev.Only Lokalise translation updates come from main; it merged without conflicts.
Built as part of the whole workspace (LoopWorkspace scheme, iOS Simulator) with every submodule at its merge commit.
Please merge with "Create a merge commit" (not squash or rebase); otherwise the merge history is lost and dev will conflict with next-dev again.