You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: