Update language file's #716
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
awawa-dev
added a commit
that referenced
this pull request
Jan 25, 2024
* Update translations by @AstaRom * update license * Disable cache before release build * Update language file's (#716) * Force HyperSerial detection (#732) * Add ttyACM detection * Fix * Update language file's (#736) --------- Co-authored-by: Aleksandar Jovanovic <[email protected]> Co-authored-by: Roman Astafev <[email protected]> * Update CHANGELOG.md * Fix verbose option * Update * Update language file's (#747) --------- Co-authored-by: Roman Astafev <[email protected]> Co-authored-by: Roman Astafev <[email protected]> Co-authored-by: Aleksandar Jovanovic <[email protected]>
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.
Summary
What kind of change does this PR introduce? (check at least one)
If changing the UI of web configuration, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing setups:
The PR fulfills these requirements:
Fixes: #xxx[,#xxx], where "xxx" is the issue number)To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.
Other information: