jestin
commented
11 months ago Looks great! Thanks!
I thought about using tags, and maybe that will be worthwhile, but there's not many significant milestones in this project that would make good tags. Let's see how this works for now.
Updated the GitHub Action to automatically create a release whenever a new commit successfully compiles. Additionally, made some whitespace changes (apologies if this is not wanted). However, I see one glaring issue with this solution, and I think would require a change in how commits are handled in the repo to make this cleaner:
Every release will have the exact same name, but we can begin using git tags to track versioning of the documents we actually want to release, and use these for the release names. If this convention is adopted, then the workflow can be updated to only create a release on particular versions of the document. We could tag certain commits as "v1.0", "v1.1", or whatever the case may be, and only create a release on these version numbers.
If you'd like to proceed with using tags for creating milestones in the versioning history, I'd be more than happy to help update this automation to respect those tags.