elastic / elastic/elastic-github-actions

Referencing the action starts an elastic container build step even if the action itself is skipped

Open
#35 3 comments 1 reaction 0 assignees View on GitHub
Dominant language
Shell
Stars
55
Forks
43
PR merge metrics
No merged PRs in 30d

Description

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](https://github.com/Lombiq/Open-Source-Orchard-Core-Extensions/actions/runs/10082467596/job/27876788040#step:2:1) for such a build:
![image](https://github.com/user-attachments/assets/2cbab0ff-f785-44d0-b7d5-c156bae9c3d2)

The Elasticsearch action is referenced in the action.yml file found in [this pull request](https://github.com/Lombiq/GitHub-Actions/pull/376/files), 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.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.