What does that mean? I don’t use R, so I don’t understand the reference.
Any other idea? Maybe involving GitHub Actions, Dependabot, something else? Maybe just a reminder to have a coffee date with your theme repo once in a while?
I mirror repos I use. I use gitea (I use a dedicated org), but most git hosting applications have a mirror feature. A bash script will do.
What does that mean? I don’t use R, so I don’t understand the reference.
Yes that comparison is quite niche. R evolves as a language, and so do its “add-ons”, the R packages. In my analogy Hugo is R (even if Hugo isn’t a language), the themes are R packages.
I mirror repos I use. I use gitea (I use a dedicated org ), but most git hosting applications have a mirror feature. A bash script will do.
Thanks for sharing your setup! How do you notice changes in your mirrors that might break your themes/sites, do you regularly look through their commit history?
Well… the authentic answer is I don’t worry, because I roll my own everything. I’m cool like that.
However! I do reference a lot of data sources, sometimes from git repos imported as go modules/git sub-modules/filesystem, and sometimes run into this issue. The reason I lean on git as VCS is because I can then pin to a tag or other release marker, to a version that I know works.
The reason I mirror is because git is meant for sharing, and syncing is surprising efficient. And from my personal experience: a repo is more likely to disappear from the origin repo than break something without me noticing.
Take my advice with a grain of salt, nearly everyone’s site is more complex than mine. I’ve no idea how folks track the various components they import and process and…