Argo Translation PR403 GITHUB-4872: Add New Buyer Languages #446
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
![argo-translation-integration[bot]](https://avatars.githubusercontent.com/in/75725?s=60&v=4){kind=small}
data/localizations/values/sl-SI.yml Argo Request GITHUB-4872 PR403
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.
Translation PR
This Translation PR contains translations of source language files modified #403, Argo Request GITHUB-4872. The contents of the source language files translated are after the files after the PR has been merged 2f277c3, which is also the base commit of this PR's head branch.
The Argo CI Check will be neutral until all translations have been committed to Github, at which point it will succeed. You can check a detailed status of individual translations by commenting
/argo -sin this PR.If you intend to merge from the base branch into this PR, you must wait until all translations have been committed (Argo CI Check passes). Otherwise, any commits made by Argo will overwrite changes to those files on the base branch since the Original PR was merged.
What happens if I merge this before translation is done?
After merging, after another target language file is complete, Argo will force-push the branch add-new-langs-argo-pr403 to the merge commit of #403, commit the file to the branch, and then open a new Translation PR with the same name.