Add a summary message with published link at the end of the workflow

[rambip]

While using bluebuild for the first time, I was confused. The image did build, but I had no idea where the output of the build was.
It would be very useful to display it as a clickable link, in particular for beginers.
I suggest adding this step:

- name: Summary
  shell: bash
  env:
    BB_REGISTRY: ${{ inputs.registry }}
    BB_REGISTRY_NAMESPACE: ${{ inputs.registry_namespace }}
    RECIPE: ${{ inputs.recipe }}
  run: |
    IMAGE_NAME=$(basename "${RECIPE}" .yml)
    echo "✅ Image published to ${BB_REGISTRY}/${BB_REGISTRY_NAMESPACE}/${IMAGE_NAME}"

Another idea would be to display a link to the appropriate documentation for beginners, or even to suggest commands.

[gmpinder]

The CLI currently already prints out a summary of the images that were built.

[rambip]

That's true. I did not notice.
But my point is not that the information is not present, I mean that it's not visible to the new user. Of course if you already know it, you juste have to scroll down to the right section.
As a comparison, most github actions that create a github page have a step dedicated to printing the link to the user in a way that is easy to discover, like

In the case of bluebuild, once the image was built, I had no idea what I was supposed to do (even looking at the documentation). IMHO, this means there is something missing. And I thing such a message could be very helpful.

[gmpinder]

This sounds like it would be more of a documentation issue then. We wouldn't be able to get the same result as your picture because all of the steps in the action are consolidated under a single section in your action view from your repo.

[rambip]

This sounds like it would be more of a documentation issue then. We wouldn't be able to get the same result as your picture because all of the steps in the action are consolidated under a single section in your action view from your repo.

You really can, using for example job summaries.
It is a documentation issue, but sometimes the best location for documentation is directly in the tool. And the github action is a tool.
Just to understand clearly, do you think it's a bad idea or do you think it's not a priority / you don't have time to do it ?

[gmpinder]

You really can, using for example job summaries.

You should have lead with this feature. That seems like something we could easily add.