Repository navigation
Referencing the action starts an elastic container build step even if the action itself is skipped #35
Description
Activity
Anybody with tips on how to prevent this Docker build step that happens after the job setup if we don't actually use the action?
Did it actually run? The / symbol suggests that this step was skipped.
No, that's the point. The build step runs even if the action doesn't.
The Elasticsearch action is conditionally called in a workflow, but even when it's not run, the container build step still runs. Here's an example for such a build:
The Elasticsearch action is referenced in the action.yml file found in this pull request, which is conditionally called in the build-and-test-orchard-core.yml file.
Is this normal behavior, or can it be prevented somehow? The container build step shouldn't run when the Elasticsearch setup step doesn't.