Git is really bad at identifying the correct Python function
in the diff hunk headers (this is a change in Metadata.sign()):
@@ -384,7 +384,7 @@ class Metadata(Generic[T]):
Amazingly there is much better context detection built-in, just not
enabled. The same diff hunk headers with this commit looks like:
@@ -384,7 +384,7 @@ def sign(
Signed-off-by: Jussi Kukkonen <jkukkonen@google.com>
A really specific bug occurred on CI runs on all Windows machines
https://github.com/theupdateframework/python-tuf/runs/5467473050?check_suite_focus=true
where we weren't able to verify that what was generated is the same
as the stored on Git.
After research with Jussi, we found out that the problem comes not
from the content of the file that was generated, but because on Windows
Git proactively replaced all line endings for text files with CRLF symbol
("\r") this made the locally stored JSON files different from the one
generated.
We want to make sure such bugs doesn't occur again and that's why we
disable this behavior for all JSON files.
Signed-off-by: Martin Vrachev <mvrachev@vmware.com>
For compatibility with Windows systems, declare repository_data
files to always have LF line endings on checkout.
A trailing "/**" matches everything inside, with infinite depth.
Signed-off-by: Teodora Sechkova <tsechkova@vmware.com>
