Closed martinbryant closed 5 months ago
Is the issue here to update the readme then?
The tag isn't for automation, it's to make it easier to identify which commit corresponds to each package version, and to get GitHub to notice that there is a new release:
I'll update the README to say that, but I think we should keep the step.
@martinbryant see #24
When doing the version 1 release, I did not tag the commit as per the readme so the github action uses the version identified in the AgGrdi.fsproj file to add as a tag