There is currently no way to get custom outputs from an action that does not have outputs at all, for example because it was modelled wrongly or because the outputs were just added by the action developer. If I were to create a PR to fix that, how would you prefer it? I see three options: • Make any action have custom outputs available • Make

ExternalActionStep

have a function

withCustomOutputs()

• Make

ExternalActionStep

have a property

withCustomOutputs

I'd try merging the concepts of action and action with outputs (since given what you wrote, any action can have outputs), so the first option seems to be the most compelling one

Not sure how the last comment is related to my question. But yeah, it is actually a theoretical problem right now. When playing with how to set the

environment

in the other thread I had to search for an action that has outputs, and thought that all should potentially have outputs to keep the flexibility the lib has in most other places.

Let me put it like this: I'd like to track it as an issue in GH and focus on real problems/missing features first :)

Yeah, it's a dance on the volcano 😄

Cool, thanks! Before I review, could you resolve the conflicts?

Ouch, that package refactoring is pure poison for that one. 😄

@Vampire thank you, it's not only a feature but also simplification of internals ❤️

Yep, with no distinction necessary it simplifies things of course :-)

can I also ask you to update the docs? unfortunately we don't yet have kotlinx-knit (or equivalent) that would have catch it in the original PR

CI now fails, I also see some other minor issues I’d like to discuss - are you fine with just fixing the docs for tomorrow’s release, and making this refactoring as a separate PR without rush?

Oh no. 🙈 Sure, no problem.

awesome, thanks! will take care of them today evening

rebased 🙂

great job, danke 🙇

Immer gerne :-)