Re: [GSoC PATCH v9 3/5] repo: add the field layout.bare
- From
Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
- Date
- Aug 14, 2025, 22:18 UTC
- Message-ID
- <1ABC1E05-BEE9-4E17-8C6C-8BB4127378BF@gmail.com>
- In-Reply-To
- <xmqqfrdt3feh.fsf@gitster.g>
> I also care about future-proofing, though. When Git is built with > WITH_BREAKING_CHANGES=YesPlease, this test would break as the > default reference backend will be reftable in that alternate world, > wouldn't it?
To be honest, it wouldn't matter what are the keys selected for testing this behavior. I'm only using references.format because it was the first that I implemented. But given that, I can also change their order to something like:
[1/5] repo: declare the repo command [2/5] repo: add the field layout.bare [3/5] repo: add the field layout.shallow [2/5] repo: add the field references.format [5/5] repo: add the --format flag
This way, this tests could be placed in 3/5 and using layout.bare and layout.shallow as keys.
Thanks!