I think this is the sequence to create the tag, and then in the GH web UI there is a spot to link the tag you make into a release that will show up on the projects primary page.
If the pdfs have a date stamp (or version stamp if you use semantic versioning for the releases) they can then be linked to the code.
git commit -am "my awesome code is updated and ready for release"
git tag -a "v2021-03-31" -m "tagging March 31 release"
git push
from simon
I think this is the sequence to create the tag, and then in the GH web UI there is a spot to link the tag you make into a release that will show up on the projects primary page. If the pdfs have a date stamp (or version stamp if you use semantic versioning for the releases) they can then be linked to the code.
git commit -am "my awesome code is updated and ready for release" git tag -a "v2021-03-31" -m "tagging March 31 release" git push