After that try to edit something in one of the archetypes/*.md files. It feels like the automatic last-updated feature is replacing the frontmatter in these files. Archetypes (the folder) is NOT added to my content folders in Front Matter.
In GoHugo the files in archetypes are templates for new content files. They should not be handled like "real" content files. Apart from that, they are NOT content files because I have not added them to the content file type config. I would not expect Front Matter to touch these files in any case.
Edit: I am not 100% sure it's frontmatter, but it feels like that, because I have no other plugin or tool that would exchange some code ({{ .Date }}) with the actual current datetime stamp.
I think I might have come upon a bug.
My repo is at https://github.com/davidsneighbour/kollitsch.dev, run `npm install`, `npm run build:frontmatter` to create the frontmatter config.
After that try to edit something in one of the `archetypes/*.md` files. It feels like the automatic last-updated feature is replacing the frontmatter in these files. Archetypes (the folder) is NOT added to my content folders in Front Matter.
In GoHugo the files in `archetypes` are templates for new content files. They should not be handled like "real" content files. Apart from that, they are NOT content files because I have not added them to the content file type config. I would not expect Front Matter to touch these files in any case.
Edit: I am not 100% sure it's frontmatter, but it feels like that, because I have no other plugin or tool that would exchange some code (`{{ .Date }}`) with the actual current datetime stamp.
<!-- github-sync-id:1319654491 -->
@davidsneighbour, this was indeed coming from the extension. An extra check is implemented only to perform the update on content located in your content folder.
@davidsneighbour, this was indeed coming from the extension. An extra check is implemented only to perform the update on content located in your content folder.
<!-- github-comment-id:1197905672 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I think I might have come upon a bug.
My repo is at https://github.com/davidsneighbour/kollitsch.dev, run
npm install,npm run build:frontmatterto create the frontmatter config.After that try to edit something in one of the
archetypes/*.mdfiles. It feels like the automatic last-updated feature is replacing the frontmatter in these files. Archetypes (the folder) is NOT added to my content folders in Front Matter.In GoHugo the files in
archetypesare templates for new content files. They should not be handled like "real" content files. Apart from that, they are NOT content files because I have not added them to the content file type config. I would not expect Front Matter to touch these files in any case.Edit: I am not 100% sure it's frontmatter, but it feels like that, because I have no other plugin or tool that would exchange some code (
{{ .Date }}) with the actual current datetime stamp.Thanks for opening the issue @davidsneighbour, will have a check on this.
@davidsneighbour, this was indeed coming from the extension. An extra check is implemented only to perform the update on content located in your content folder.