Add Ancestors (plural) method to GitInfo

[jmooring]

We recently added an Ancestor method, but I suspect most people will want to render the full history, or the last N changes, requiring a recursive partial similar to:

{{ partial "inline/changelog.html" .GitInfo }} 

{{ define "_partials/inline/changelog.html" }}
  {{ with . }}
    {{ partial "inline/changelog.html" .Ancestor }}
    {{ .CommitDate.Format "2006-01-02" }}: {{ .Subject }}<br>
  {{ end }}
{{ end }}

Conceptually this new method would align with the .Page.Ancestors method that is commonly used when rendering a breadcrumbs UI component.

{{ with .GitInfo }}
  {{ range .Ancestors }}
    {{ .CommitDate.Format "2006-01-02" }}: {{ .Subject }}
  {{ end }}
{{ end }}

OR

{{ with .GitInfo }}
  {{ range .Ancestors | first 5 }} 
    {{ .CommitDate.Format "2006-01-02" }}: {{ .Subject }}
  {{ end }}
{{ end }}

The above would give you the last 5 changes.

If this is practical from a performance standpoint (and it may not be), and we implement an Ancestors method, it seems like the Ancestor method (singular) could be removed.

[bep]

If this is practical from a performance standpoint (and it may not be), and we implement an Ancestors method, it seems like the Ancestor method (singular) could be removed.

The history is fast to navigate, but since we're not using Go's new iter package (longer story), we need to create a slice with all items, which is unfortunate if the history is long (e.g. the Hugo docs repo) and you only want the last n items.

But I guess we can test it out on the Hugo Docs repo and see how it flies. The penalty would only be paid by those who want to navigate the ancestors, so I guess it should be OK.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.