Open jmooring opened 1 week ago
Note that using the ignoreFiles
setting in the root of the site configuration produces the desired results, but we've been recommending the use of mount exclusions instead.
The issue title here isn't correct. We do honor mount ignore files setting for all builds, meaning: We don't build them. We trigger a noop build when those files changes, which I guess is a difference between the global setting, but I would say that that is undocumented behaviour. We could and should probably skip builds for change sets that don't resolve to any files on the file system.
Note that using the ignoreFiles setting in the root of the site configuration produces the desired results
ignoreFiles
only works for content
files, which isn't my desired result.
Thanks for the clarification. This obviously isn't a high priority.
I'm not sure if this is a bug or an enhancement... or perhaps there's a good reason for the current behavior.
With the above, when I edit content/posts/post-1.md ...
I can see from the last line that no files have changed, which is good, but it seems like we shouldn't be doing the other stuff.
Tested with hugo v0.135.0-DEV-a619deec1827ea2d601a9b3708d1375c1eca3c5c+extended linux/amd64