-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
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
Allow setting textdomain manually #184
Comments
You could also just do
No need to reimplement this in this action :) |
@swissspidy I have a similar issue and your trick doesn't work. My plugin is availabe on "/dist", and it's name is "my-plugin". with the following config:
I get the following github error:
If I remove this part:
I get the original issue, What should I do? |
I found a similar issue with the WP plugin, which could be resolved with |
Setting I will consider adding support for In the meantime I recommend just renaming your folder. - name: Build plugin
run: |
mv ./dist ${{ runner.temp }}/my-plugin
- name: Run plugin check
uses: wordpress/[email protected]
with:
build-dir: ${{ runner.temp }}/my-plugin |
@swissspidy Thanks, it worked out perfectly ;) |
First off thank you very much for the github action. I already implemented it in our plugin boilerplate CI: https://github.com/JUVOJustin/wordpress-plugin-boilerplate
However when the workflow clones the repo with a simple
- uses: actions/checkout@v4
And the repository has a different name than the textdomain configured in the plugin header, the pipeline seems to use the folders name inside the github action which is the repo name by default.
Example:
Repo: my-awesome-plugin
Textdomain: awesome-plugin
Result:
Mismatched text domain. Expected 'my-awesome-plugin' but got 'awesome-plugin'.
By passing the expected textdomain to the action this could be solved.
The text was updated successfully, but these errors were encountered: