Improved
- Template updates no longer nag about customized files (#845): updating the site template now records the template version in your garden (
.digitalgarden-template-version). From then on, "update available" only appears when a newer template release is out, not because you've changed template files yourself.- If your template files differ from the latest template, the settings page tells you how many and offers Re-apply template, which opens a pull request that restores them.
- Gardens that haven't updated since this release keep the old file comparison until their next template update. If the plugin keeps saying an update is available even though you're up to date, use Mark as up to date in the settings to record the current version.
- Template updates are a single commit: the update pull request now contains one commit instead of one per file, and a failure part way (for example GitHub rate limiting) no longer leaves a half-finished update branch behind.