Closed csaba-almasi-neonomics closed 10 hours ago
Thanks for reporting this issue, don't forget to star this project if you haven't already to help us reach a wider audience.
+1
Hi @csaba-almasi-neonomics, according to the documentation, if you use files_yaml*
input, the outputs will be prefixed by the keys you specified, so you would need to change.
-- changed_module_folders: ${{ steps.changed_directories.outputs.all_modified_files}}
++ changed_module_folders: ${{ steps.changed_directories.outputs.base_modules_all_modified_files}}
For more information view the documentation here
Is there an existing issue for this?
Does this issue exist in the latest version?
Describe the bug?
When using
files_yaml_from_source_file
orfiles_yaml
input , standard outputs likeall_changed_files
is not returned.Sample workflow file
The output is:
So the issue is not in the
changed-files.yaml
config. Is this the expected behavior here? I read through the documentation thoroughly and have seen no reference to outher outputs being absent when using the yaml based file input approach. Referencing the job output in subsequent jobs also yields''
which signals that the output is null or empty.When looking at debug logs I do see
base_modules_modified_files
and similar outputs.Why is this a problem?
If there is no globally returned changed file list, I have to set the outputs for the job one-by-one for each key in the yaml config
To Reproduce
Using the
files_yaml
orfiles_yaml_from_source_file
with any configuration will yield the same result.What OS are you seeing the problem on?
ubuntu-latest or ubuntu-22.04
Expected behavior?
Either: A. The action output is there for
all_changed_files
or similar B. There is a an output that handles changed files based on the associated keys such asC. It is documented that using the above mentioned inputs only yields
changed_keys
output and yaml key specific outputs likebase_modules_modified_files
etc.Relevant log output
Has all relevant logs been included?
Code of Conduct