In order for us to add in ci/cd (#48), we'd either need to be constantly generating same-named build files and overwriting them, or have versioned names. if we have versioned names, then we'd need some unique identifier tying it to the code base, which is either the SHA hash or an actual version number.
Since the SHA hash can't be sorted easily, we'd need to either add in a build timestamp, or have versions of the dotfiles using the automated semver stuff.
I'll be going with the automated semver stuff since it seems like a better solution long term, and makes for an easy 1:1 mapping between the codebase and releases.
Background
In order for us to add in ci/cd (#48), we'd either need to be constantly generating same-named build files and overwriting them, or have versioned names. if we have versioned names, then we'd need some unique identifier tying it to the code base, which is either the SHA hash or an actual version number.
Since the SHA hash can't be sorted easily, we'd need to either add in a build timestamp, or have versions of the dotfiles using the automated semver stuff.
I'll be going with the automated semver stuff since it seems like a better solution long term, and makes for an easy 1:1 mapping between the codebase and releases.