Add tagging action

[nb1701]

Adds an action to tag the repo. Partially addresses civiform/civiform#4763

[nb1701]

I tested this with some gh shenanigans and it seems to work. Soon, the "Create Release" action on the civiform repo will trigger this action with the given release version. Then, we'll be able to have people use the specific tag on this repo that matches the tag of the release they are trying to deploy.

[gwendolyngoetz]

When we get to running this on the release call in civiform/civiform do we want to prevent this from manually being run in order to prevent them from getting out of sync?

[gwendolyngoetz]

Suggested change

	git tag -a ${{ github.event.inputs.release_number }} -m "Release ${{ github.event.inputs.release_number }}"
	git tag ${{ github.event.inputs.release_number }} --message="Release ${{ github.event.inputs.release_number }}"

I had to look up the -a since I hadn't used it. I'd remove it unless you found a reason it needs to be explicitly set. The docs say:

If -m or -F is given and -a, -s, and -u are absent, -a is implied.

[nb1701]

The -a is the actual tag, and the -m is a message for the tag. I have it slightly different here, but I guess it doesn't need to be so.

[nb1701]

It would seem git tag -m doesn't really work on its own, despite what it says here.

[nb1701]

Oh, it's git tag <tag> -m <whatever>. I think I'll just remove the -m and -a entirely.

[nb1701]

Nope, we still want the -m or else it just fills it in with the commit message of the commit it's tagged on.

[nb1701]

When we get to running this on the release call in civiform/civiform do we want to prevent this from manually being run in order to prevent them from getting out of sync?

Is that a thing we can do? Might still be nice to have the option to run it manually in case things go sideways, but I don't know. It's pretty easy to delete a bad tag if we need to.

[gwendolyngoetz]

Suggested change

	git tag ${{ github.event.inputs.version }} -m "${{ github.event.inputs.version }}"
	git tag ${{ github.event.inputs.version }} --message="${{ github.event.inputs.version }}"

Using the full arg name make it easier to understand at a glance.

[gwendolyngoetz]

When we get to running this on the release call in civiform/civiform do we want to prevent this from manually being run in order to prevent them from getting out of sync?

Is that a thing we can do? Might still be nice to have the option to run it manually in case things go sideways, but I don't know. It's pretty easy to delete a bad tag if we need to.

I thought there was a trigger type that let use trigger it, but not in the ui. I might be remembering wrong.

[nb1701]

Ah yeah, there's https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#workflow_call, but I'm not sure if that works cross-repo. https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#repository_dispatch might also work. I'll take a look at those when I work on the civiform release action trigger.