Composite action vs reusable workflow

[mariajgrimaldi]

Consider rewriting this #1 reusable action as a composite action instead #1 (comment):

I was thinking that maybe instead of creating a workflow for building Docker images, it might be more convenient to do it as a GitHub Action. This way, each team or company could create their own workflow using the action, which would be much more flexible.

Additionally, this would allow us to easily consider the future of pushing to different Docker registries. Centralizing everything in a GitHub Action would give us the flexibility to adapt to different needs in the future without having to modify multiple workflows.

What do you think? Do you think we could evaluate the possibility of doing it as an action instead of a workflow?

Here we should have a conversation about which implementation we prefer.

[jfavellar90]

The discussion is still open. It is a reusable workflow for now.