🚀 Create Release Workflow

[keithrfung]

Checklist

🚨Please review the guidelines for contributing to this repository.

• 🤔 CONSIDER adding a unit test if your PR resolves an issue.
• ✅ DO check open PR's to avoid duplicates.
• ✅ DO keep pull requests small so they can be easily reviewed.
• ✅ DO build locally before pushing.
• ✅ DO make sure tests pass.
• ✅ DO make sure any new changes are documented.
• ✅ DO make sure not to introduce any compiler warnings.
• ❌AVOID breaking the continuous integration build.
• ❌AVOID making significant changes to the overall architecture.

Description

This github action makes use of original build tasks to create each of the artifacts and zips them up for easy consumption by the c# package

Here's an example:
https://github.com/microsoft/ElectionGuard-SDK-C-Implementation/releases/tag/untagged-674328eb13139d72db61

The build from this will update the badge on the Readme.

Closes #25
Closes #27

[AddressXception]

just one question to address

[AddressXception]

should this be a configurable var? is every release going to have this same tag? maybe I'm just not familiar with actions enough yet

[keithrfung]

So ordinarily yes. This release tag is usually pulled in from the branches tag. However, this isn't being started by a branch but by a milestone so there's no associated branch tag. If you look at the release that is made, you'll notice the tag isn't set because there isn't an existing v1.0.0 tag. I could try setting it to say untagged if you prefer? If someone makes a tag called untagged it'll start hooking up to that.

It's an oddity where the tag is required even if it's not used.

[AddressXception]

im just thinking that we'll have to update this when we update the milestone. would prefer to not do that, but it sounds like there isnt a good solution at the moment

[keithrfung]

This issue was added to solve this: #28