Adding post-artifact action and updating README

[gvegayon]

• Ports the initial work I was doing from https://github.com/gvegayon/actions
• Updates the readme.
• In the port, adds new workflow for testing the action.

Note that the artifact is working as we got four different comments from github-actions[bot]!

[github-actions]

Thank you for your contribution @gvegayon 🚀! Your readme-ubuntu-latest is ready for download 👉 here 👈!
_{(The artifact expires on 2025-01-02T16:20:25Z. You can re-generate it by re-running the workflow here)}

[github-actions]

Thank you for your contribution @gvegayon 🚀! Your readme-macos-latest is ready for download 👉 here 👈!
_{(The artifact expires on 2025-01-02T16:20:25Z. You can re-generate it by re-running the workflow here)}

[github-actions]

Thank you for your contribution @gvegayon 🚀! Your readme-windows-latest is ready for download 👉 here 👈!
_{(The artifact expires on 2025-01-02T16:20:25Z. You can re-generate it by re-running the workflow here)}

[github-actions]

Thank you for your contribution @gvegayon 🚀! Your readme-rocker is ready for download 👉 here 👈!
_{(The artifact expires on 2025-01-02T16:20:25Z. You can re-generate it by re-running the workflow here)}

[github-actions]

Thank you for your contribution @gvegayon 🚀! Your readme-macos-latest is ready for download 👉 here 👈!
_{(The artifact expires on 2025-01-20T23:17:59Z. You can re-generate it by re-running the workflow here.)}

[github-actions]

Thank you for your contribution @gvegayon 🚀! Your readme-ubuntu-latest is ready for download 👉 here 👈!
_{(The artifact expires on 2025-01-20T23:17:59Z. You can re-generate it by re-running the workflow here.)}

[github-actions]

Thank you for your contribution @gvegayon 🚀! Your readme-windows-latest is ready for download 👉 here 👈!
_{(The artifact expires on 2025-01-20T23:17:59Z. You can re-generate it by re-running the workflow here.)}

[github-actions]

Thank you for your contribution @gvegayon 🚀! Your readme-rocker is ready for download 👉 here 👈!
_{(The artifact expires on 2025-01-20T23:17:59Z. You can re-generate it by re-running the workflow here.)}

[gvegayon]

I changed how to id the messages, that's why we now have two sets of them, @dylanhmorris and @swo.

[dylanhmorris]

Thanks for this, @gvegayon. A few questions and comments.

[dylanhmorris]

@gvegayon lmk when this is ready for re-review

[gvegayon]

Ready for re-review, @dylanhmorris!

[dylanhmorris]

This looks very good; thanks @gvegayon! One question: perhaps I am missing something, but it appears that there there is no explicit error raised if the user attempts to trigger the action with an event other than a PR. I am not sure the actual errors that will occur in those cases be will be informative, so I think we should add an explicit informative error, but I am happy to be persuaded otherwise.

[gvegayon]

This looks very good; thanks @gvegayon! One question: perhaps I am missing something, but it appears that there there is no explicit error raised if the user attempts to trigger the action with an event other than a PR. I am not sure the actual errors that will occur in those cases be will be informative, so I think we should add an explicit informative error, but I am happy to be persuaded otherwise.

If we add an error, then we would be forcing the user to use the if: {{ on PR only }} condition, which takes it back to the original design in which we were making the action run only on PRs. In other words, if we are going into the trouble of erroring when the user is not calling this on a PR, why don't we make it run on PRs only by construction?

[gvegayon]

Added an error msg as discussed, @dylanhmorris!

[dylanhmorris]

LGTM, thanks @gvegayon!