holyhope/Test WordPress language files

Check internationalization files for WordPress plugins for being up-to-date.

View on GitHub

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Maintainedlast commit Jun 23, 2025
License: MPL 2.0

Pinned Snippet

workflow.ymlSHA-pinned

uses: holyhope/test-wordpress-languages-github-action@8ed87ecf3a8eb1824d3f62b450d0cb9e28890ec9 # v4.0.2

tags can be moved; commit SHAs can't. why a SHA?

Inputs

name	description	required	default
slug	Plugin or theme slug.	yes	—
source	Directory to scan for string extraction.	no	.
pot_file	Path to an existing POT file to use for updating. Default: `{source}/{slug}.pot`	no	—
po_path	PO files to update or a directory containing multiple PO files. Type: multi-line string Default: all PO files in the source directory with the same prefix as the POT file.	no	—
languages_directory	Path to the languages directory	no	languages
ignored_patterns	Pattern to ignore when checking the POT file changes. Type: multi-line string	no	# Copyright (C) "POT-Creation-Date: X-Generator:
domain	Text domain to look for in the source code, unless the `ignore-domain` option is `true`. Default: the "Text Domain" header of the plugin or theme is used.	no	—
ignore_domain	Ignore the text domain completely and extract strings with any text domain.	no	false
skip_js	Skips JavaScript string extraction. Useful when this is done in another build step, e.g. through Babel.	no	false
skip_php	Skips PHP string extraction.	no	false
skip_blade	Skips Blade-PHP string extraction.	no	false
skip_block_json	Skips string extraction from block.json files.	no	false
skip_theme_json	Skips string extraction from theme.json files.	no	false
skip_audit	Skips string audit where it tries to find possible mistakes in translatable strings.	no	true
exclude	List of files and paths that should be skipped for string extraction. Simple glob patterns can be used, i.e. `foo-.php` excludes any PHP file with the `foo-` prefix. Leading and trailing slashes are ignored, i.e. `/my/directory/` is the same as `my/directory`. The following files and folders are always excluded: node_modules, .git, .svn, .CVS, .hg, vendor, .min.js. Type: multi-line string Default: None	no	—
include	List of files and paths that should be used for string extraction. If provided, only these files and folders will be taken into account for string extraction. Simple glob patterns can be used, i.e. `foo-*.php` includes any PHP file with the `foo-` prefix. Leading and trailing slashes are ignored, i.e. `/my/directory/` is the same as `my/directory`. Type: multi-line string Default: None	no	—
location	Whether to write `#: filename:line` lines. Note that disabling this option makes it harder for technically skilled translators to understand each message’s context.	no	true
headers	Array in JSON format of custom headers which will be added to the POT file.	no	—
file_comment	String that should be added as a comment to the top of the resulting POT file.	no	—
package_name	Name to use for package name in the resulting POT file's `Project-Id-Version` header. Overrides plugin or theme name, if applicable.	no	—
fail_on_diff	Whether to fail the build if there are differences in the POT file.	no	true
fail_on_warning	Whether to fail the build if there are warnings.	no	true
wp_cli_path	Path to the WP-CLI binary. To use a custom version of WP-CLI, see the [`install-wp-cli` GitHub action](https://github.com/marketplace/actions/install-wp-cli) Default: Downloaded from the official WP-CLI website.	no	—

Outputs

name	description
patch_path	Path to the patch file containing the changes to apply.
warnings_path	Path to the file containing warnings.