Block style versus Flow style for YAML configuration readability

When authoring a YAML configuration file that will be edited frequently by multiple contributors, the goal is to select a style that remains easy to read while producing clear, line‑based differences in version control.

Block style relies on indentation and line breaks, which enhances readability for hierarchical data but can lead to deep indentation that obscures structure; flow style uses explicit braces and brackets, offering a compact, JSON‑like representation that may become difficult to parse visually when nested arrays or maps appear on a single line. The specification permits mixing both styles within the same document, allowing a hybrid approach.

Given these trade‑offs, it is unclear which style—or combination—provides the best balance of human readability and diff friendliness for typical configuration updates, especially when dealing with moderately nested maps and sequences.

Which style yields cleaner line‑based diffs when a leaf value is changed? Does a hybrid approach improve readability without sacrificing diff clarity? Which style is preferable for deeply nested structures that require frequent edits?