Pat Hawks

@ashmaroli Yes, we would have to do some manual work rather than relying on Git, but we are already setting the commit message manually, so this would be no different...

Maybe also add a comment to the PR letting the author/maintainers know that there are new conflicts that need to be resolved? I'm not sure exactly how this would work...

I wonder if this requires upstream changes to [changelog](https://github.com/parkr/changelog/blob/cef0141074f9b8cc85a225bb4edca5278114e997/changelog.go#L77-L108), or if it would be better just [appending to `Summary`](https://github.com/parkr/auto-reply/blob/a0e5a92d34d5982f0b4ceedefa86bb7f24e27e6d/chlog/merge_and_label.go#L291-L294)?

We should still be [merging the override](https://github.com/jekyll/jekyll/commit/d01f7943debf08dee645990ddb0e00d59cf846bb#diff-7995fea725f957f33d29b000f4cba24dR108). Can you provide a test that to reproduce this issue?

Hey @groundh0g! I worked with you on a few PRs to plusjade/jekyll-bootstrap way back when :wave: I think this is a really cool idea and I see the use case...

> So, the terrible hack is to move the collection content to their own pages, segregated by folder. That way, markdown files (with YAML headers) in the same path are...

Thinking out loud: Not all documents are rendered at the same time. If posts are rendered before collections, it would make sense for the content of collections documents to appear...

> Explains the content being populated, but the output being null, right? Right. Not sure there's a great solution here.

Related: #3738 #3738 #4905

Too, I suppose, different MarkDown processors could render code blocks differently. We should just be very clear about the behavior of the `highlight` tag 👍🏼