Build more binary releases

[wc7086]

No description provided.

[aspacca]

@wc7086 thanks for the contribution, please see my comments

[wc7086]

This is modified from the automated yaml of other projects. Because I don’t know everyone’s preferences, and I didn’t consider some automated programs, so I didn’t write very well. It has now been modified according to your requirements.

[wc7086]

I made some mistakes which led to more commits. Should I open another PR or you use the squash mode to merge my commits?

[stefanbenten]

We can squash them 👍

[wc7086]

In order to facilitate the tracking of the problem, I think that the version number should be written into the cmd.go and the Commit ID should be added. What do you think?

[aspacca]

In order to facilitate the tracking of the problem, I think that the version number should be written into the cmd.go and the Commit ID should be added. What do you think?

that's what happens here: https://github.com/dutchcoders/transfer.sh/pull/395/files#diff-87db21a973eed4fef5f32b267aa60fcee5cbdf03c67fafdc2a9b553bb0b15f34R126

[wc7086]

that's what happens here: https://github.com/dutchcoders/transfer.sh/pull/395/files#diff-87db21a973eed4fef5f32b267aa60fcee5cbdf03c67fafdc2a9b553bb0b15f34R126

This is the tag, not the Commit ID.
I circled the Commit ID in the image below.

[aspacca]

This is the tag, not the Commit ID.

the tag points to a commit, if you build from a not tagged commit it will print something like v1.x.x-commit