Clarify that span shouldn't be in translated READMEs#8754
Merged
litetex merged 1 commit intoTeamNewPipe:devfrom Aug 25, 2022
Merged
Conversation
Collaborator
|
"commit" this mistake haha |
opusforlife2
approved these changes
Aug 12, 2022
Contributor
Author
|
@opusforlife2 this is a pun that works on multiple levels. :P |
litetex
approved these changes
Aug 25, 2022
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
3 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.
What is it?
Description of the changes in your PR
Clarify that the hidden update span should not be included in translated READMEs. People commit this mistake often.
Due diligence