Ignore venv from message compilation #2261
Open
Conversation
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
ulgens
force-pushed
the
compilemessages-ignore-venv
branch
from
a9248e8 to
b4fe214
Compare
The goal is to exclude 3rd parties from compilemessages input
ulgens
force-pushed
the
compilemessages-ignore-venv
branch
from
b4fe214 to
44b5b46
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
The goal is to exclude 3rd parties from
compilemessagesinputWe were having a Docker build issue last week, arising from a faulty .po file in one of our dependencies. We no longer have the issue, but the change here ensures it won't happen again.