Fix Foreigner Translators AGAIN #559
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
github-actions
bot
added
Status: Merge Conflict
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
SimpleStation14
changed the title
Signed-off-by: Mnemotechnican <69920617+Mnemotechnician@users.noreply.github.com>
DangerRevolution
approved these changes
Jul 17, 2024
DEATHB4DEFEAT
approved these changes
Jul 18, 2024
SimpleStation14
added a commit
that referenced
this pull request
Jul 18, 2024
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.
Description
Previous fix made it so that foreigner translators use no power (due to being parented off of the wrong proto).
So I took some time to rearrange translators.yml because the file was shitfucked and that's what caused the mistake in the first place.
This time it was made sure that:
Changelog
🆑