keisukeyamashita/Side effect changed files

GitHub Actions to trigger side effect based on changed files

Trust Signals

name	description	required	default
bypass	Bypass the check and outputs for the matching files.	no	—
dir_names	Output unique changed directories instead of filenames.	yes	false
dir_names_max_depth	Limit the directory output to a maximum depth.	no	—
escape_json	Escape JSON special characters.	no	false
files	Files to check for the side effects.	yes	—
filters	Filter the results with glob pattern.	no	—
include	Include the result glob pattern to match the inputs.	no	—
json	Output files in JSON format.	no	false
mapping	Mapping of the files and its side effects. If you specify `mapping_file` field, it will be merged with the mapping.	no	—
mapping_file	Mapping file of the files and its side effects. If you specify `mapping` field, it will be merged with the mapping.	no	.github/side-effect.yml
matrix	Output files in a format that can be used for GitHub Action's matrix strategy.	no	false
merge	Merge the files and its side effects.	no	false
auto	Auto-generate the mapping for a known ecosystem. Currently supports `terraform`. When set to `terraform`, the action scans `*.tf` files in the current working directory, parses `module "..." { source = "..." }` blocks with local sources (paths starting with `./` or `../`), and produces a mapping where the consumer directory's tf files are output when any file under the referenced module directory changes. The generated mapping is merged with any `mapping` / `mapping_file` you provide.	no	—

name	description
changed	Boolean value indicating whether the files have changed.
files	List of changed files.
files_count	Number of the files.