Sorry I wasn’t paying too close attention to the development of pandoc-templates. Hopefully this thread can serve as a note to those who used pandoc-templates. Probably this should be converted to pandoc wiki once I gathered enough information.

So from my vague memory, it seems that the “git structure” of pandoc has changed. Some submodules becomes git subtree. One of the consequence is the removal of jgm/pandoc-templates. Please correct if there’s any info wrong up to now.

Anyhow, jgm/pandoc-templates no longer exists. First of all, can I suggest we never do that? Deleting a GitHub repository has a huge consequence if it is the “upstream.” Right now, my fork appears to be forked from https://github.com/adityam/pandoc-templates. In short, GitHub will automatically grant the oldest existing fork as the upstream of all remaining forks if the original upstream is deleted. But then as an earliest upstream, it often are far lag behind in terms of commits of the original upstream. e.g. from mine I see “This branch is 282 commits ahead of adityam:master.” I think a better way to deprecate a project is to archive it (Settings > Archive this repository).

Another question is that what is the current recommended method of having custom templates which can receives update from upstream from time to time? Or do we now has a better way of managing templates (such as template snippets)?

--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/70c082c6-8546-4ff0-b3c6-52c4b0b07c44%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.