Lack of .shed.yml file for a tool or set of tools results in action deciding to do nothing but not giving an error

[pcm32]

Thanks again for this great action, we use it constantly.

I've noticed that if the .shed.yml file is not present in the directory of modified tools, the action doesn't fail but following steps don't take care of the tools. Maybe this is an issue on our CI setup, but I wonder if it would be better if part that determines commit ranges, repos and chunks fails instead alerting the user of the lack of a .shed.yml file? I took me a bit of time to realise it was missing.

[nsoranzo]

The .shed.yml file is used to identify directories that should contain tools/workflows from directories to ignore, so I don't see how we can support this unfortunately.

[pcm32]

No, of course, you cannot support it, I meant it should fail more explicitly rather than not doing anything in the following steps. From the outside, it looks like everything is successful + skipped = succes, which is misleading.

[bernt-matthias]

Actually we have such a check

planemo-ci-action/planemo_ci_actions.sh

Line 126 in fd4d12c

echo "Tool $TOOL not in changed repositories list: .shed.yml file missing" >&2

I would hope that this fixes it? #55