but it's not cool at all
# general
s
but it's not cool at all
h
It’s a little more idiomatic to register those tasks as
build.docker
and
push.docker
, which would solve the problem.
The logic being that a goal is some generic kind of thing that needs doing, and a task is one of the several things that can do it.
E.g., if there were some docker competitor,
build
and
push
would still apply to it.
E.g., it’s
compile.java
and
test.junit
, not
java.compile
and
java.test
, if that analogy is helpful.
Oh, I see @enough-analyst-54434 has already suggested something similar.