# Cases where `yamlruff fix` differs from yamlfix, with the reason. A case not
# listed must match yamlfix byte for byte (see tests/yamlfix_acceptance.rs).
tests/unit/test_services.py::TestFixCode::test_anchors_and_aliases_with_duplicate_merge_keys#62	DIFFERENT MEANING: yamlfix merges repeated `<<` keys into one list; yamlruff reports key-duplicates and leaves the document
tests/unit/test_services.py::TestFixCode::test_fix_code_functions_emit_debug_logs#58	same meaning: yamlfix turns an empty file into one newline; yamlruff leaves an empty file empty
tests/unit/test_services.py::TestFixCode::test_fix_code_preserves_indented_comments[---\n- program:\n  # Keep comments!\n]#11	same meaning: yamlfix keeps a comment at an indent that comments-indentation rejects; yamlruff makes the output lint-clean
tests/unit/test_services.py::TestFixCode::test_fix_code_respects_jinja_variables_with_operations#67	same meaning: yamlfix wraps after the width (an 81-column line); yamlruff wraps within line-length
tests/unit/test_services.py::TestFixCode::test_fix_code_respects_many_jinja_variables#66	same meaning: yamlfix wraps after the width (an 82-column line); yamlruff wraps within line-length
