Current implementation: deployment-settings.yml uses defaults when missing but not when empty.

Consider either:

• using defaults for both missing and empty files
• documenting that empty files clear defaults

Thoughts?

Current implementation: deployment-settings.yml uses defaults when missing but not when empty.

Consider either:

• using defaults for both missing and empty files
• documenting that empty files clear defaults

Thoughts?

Shouldn't empty values skip the application of the rule (keep current setting on the repo)?

Current implementation: deployment-settings.yml uses defaults when missing but not when empty.
Consider either:

• using defaults for both missing and empty files
• documenting that empty files clear defaults

Thoughts?

Shouldn't empty values skip the application of the rule (keep current setting on the repo)?

To clarify, this change is specifically about deployment-config.yml (example here), which is the app's core configuration file. Unlike other settings files, this configuration cannot be overridden.

Regarding the original question about empty vs missing files:
This current implementation applies defaults when the file is missing, but not when the file is empty.

Please let me know if I've missed something or if you need additionnal clarification.