Bjørn Erik Pedersen 12dc9a6e4a deploy: Fix deploy defaults for non-zero flag values (e.g. maxDeletes, invalidateCDN) ... This was broken in the config rewrite in Hugo 0.112.0. The workaround is to be explicit about setting these flag values (even if just using the defaults), e.g.: ``` hugo deploy --invalidateCDN --maxDeletes 256 ``` Fixes #11127		2023-06-18 19:38:34 +02:00
..
cloudfront.go	all: gofmt -w -r 'interface{} -> any' .	2022-03-17 22:03:27 +01:00
deploy.go	Replace the old log setup, with structured logging etc.	2023-06-18 13:03:04 +02:00
deploy_azure.go	all: gofmt -w -r 'interface{} -> any' .	2022-03-17 22:03:27 +01:00
deploy_test.go	Replace the old log setup, with structured logging etc.	2023-06-18 13:03:04 +02:00
deployConfig.go	deploy: Fix deploy defaults for non-zero flag values (e.g. maxDeletes, invalidateCDN)	2023-06-18 19:38:34 +02:00
deployConfig_test.go	Create a struct with all of Hugo's config options	2023-05-16 18:01:29 +02:00
google.go	all: gofmt -w -r 'interface{} -> any' .	2022-03-17 22:03:27 +01:00