We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Right now Traduttore supports only translatable strings found in the master / default branch of a repository.
What if you have two branches in your source code repository, e.g. master and production, with both having different translatable strings?
master
production
What if you build an open source plugins where translatable strings can differ with each version (i.e. tagged release)?
I wonder if and how we can support such use cases.
The text was updated successfully, but these errors were encountered:
https://wp-translations.pro/ seems to support this too
Sorry, something went wrong.
Related: #140
No branches or pull requests
Right now Traduttore supports only translatable strings found in the master / default branch of a repository.
What if you have two branches in your source code repository, e.g.
master
andproduction
, with both having different translatable strings?What if you build an open source plugins where translatable strings can differ with each version (i.e. tagged release)?
I wonder if and how we can support such use cases.
The text was updated successfully, but these errors were encountered: