hooks should be able to pass a warning message through to the caller

[philpennock]

At present, the output from running hooks such as in the before: section is an all-or-nothing choice: the caller can use goreleaser --verbose and see them all, or they can see nothing.

It would be great if the logwriter handling supported directives in the output stream, to catch messages which really should be shown, without having the hook fail. That way, a hook could issue a deprecation warning just the same as goreleaser can.

An example of prior art which works fairly well: the GitHub Actions Workflow Directives, per https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-commands, and the ability to do something like:

echo "::notice title=Deprecated env var::saw FOO_A set but not FOO_B, we're transitioning, please use FOO_B instead"

In my particular case, there's an unusual branch which will still work, but I think it's worth having a warning show up even in the goreleaser normal output.

---

A related thing to consider then would be if hooks should be run with a particular env-var set by Goreleaser, to signal that it's running inside goreleaser, so that a hook could have a preamble such as:

if [[ -n "${GORELEASER_HOOK:-}" ]]; then
  notice() { printf '::notice title=%s::%s\n' "$MyHookName" "$*" ; }
else
  notice() { printf '%s: %s\n' "$MyHookName" "$*"; }
fi

[caarlos0]

with goreleaser-pro you can:

before:
  hooks:
  - cmd: foobar
    output: true

and i'll forward the entire output.

but your idea might be worth investigating, yes.