summaryrefslogtreecommitdiff
path: root/builtin/reset.c
diff options
context:
space:
mode:
authorLibravatar Glen Choo <chooglen@google.com>2021-10-15 13:16:29 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2021-10-15 14:30:07 -0700
commitf30e4d854bb8462d1a4da697ad95501d33fe4425 (patch)
tree1ae521bc15646602e65c7ec7353a6b2f66c54596 /builtin/reset.c
parentMerge branch 'ab/ignore-replace-while-working-on-commit-graph' into gc/use-re... (diff)
downloadtgif-f30e4d854bb8462d1a4da697ad95501d33fe4425.tar.xz
fsck: verify commit graph when implicitly enabled
Change fsck to check the "core_commit_graph" variable set in "repo-settings.c" instead of reading the "core.commitGraph" variable. This fixes a bug where we wouldn't verify the commit-graph if the config key was missing. This bug was introduced in 31b1de6a09 (commit-graph: turn on commit-graph by default, 2019-08-13), where core.commitGraph was turned on by default. Add tests to "t5318-commit-graph.sh" to verify that fsck checks the commit-graph as expected for the 3 values of core.commitGraph. Also, disable GIT_TEST_COMMIT_GRAPH in t/t0410-partial-clone.sh because some test cases use fsck in ways that assume that commit-graph checking is disabled. Helped-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com> Signed-off-by: Glen Choo <chooglen@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'builtin/reset.c')
0 files changed, 0 insertions, 0 deletions