You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using an existing theme, but did some very small modifications by copying some templates using 'theme -c' and editing them.
Over time the theme might be updated and it would be great to a) be able to see if there are updates available and b) see the diffs between my templates and the original theme.
I can do the diffs manually using git, e.g. delete the file in the themes directory, do a new 'theme -c' , and then run git diff, but I would need to do this for every single file and then also checkout the original file again. Perhaps a 'nikola theme diff' would be an option?
Another suggestion/question: when I use '--parent=' to specify a non-base theme for the '-c' command is there a way to find out where the file came from? For git tracked themes, it would be great to have the git version and url in the header of custom templates, so that one can figure out where they came from and perhaps manually can look for updates in the theme;)
The text was updated successfully, but these errors were encountered:
I'm using an existing theme, but did some very small modifications by copying some templates using 'theme -c' and editing them.
Over time the theme might be updated and it would be great to a) be able to see if there are updates available and b) see the diffs between my templates and the original theme.
I can do the diffs manually using git, e.g. delete the file in the themes directory, do a new 'theme -c' , and then run git diff, but I would need to do this for every single file and then also checkout the original file again. Perhaps a 'nikola theme diff' would be an option?
Another suggestion/question: when I use '--parent=' to specify a non-base theme for the '-c' command is there a way to find out where the file came from? For git tracked themes, it would be great to have the git version and url in the header of custom templates, so that one can figure out where they came from and perhaps manually can look for updates in the theme;)
The text was updated successfully, but these errors were encountered: