Open datapolitical opened 3 years ago
Bumping this
@datapolitical Hey, the way this works for GitHub Actions is a good guide here. What they do, is they have @v2
as a branch, then merge changes into that branch and tag as they need to. So a tag/release v2.1.1
would be a specific SHA-1 on the v2
branch. Since jekyll-remote-theme will use any reference, I'd suggest using a latest
branch here and merging changes into that branch in order to release!
Is your feature request related to a problem? Please describe the problem you're trying to solve.
I'd like to specify to always use the latest tagged release of a theme. Right now I can only specify a particular release (v2.1.1) or just let it load the latest build, which is often broken.
Describe the solution you'd like
theme@latest would get the latest tagged release.
Describe alternatives you've considered
Updating the config file every time the theme version changes (which is a real pain)