t9009-workspace-flow-fixture: implicit `bit status` in a fixture workspace does not show workspace status

[mizchi]

Summary

t/t9009-workspace-flow-fixture.sh fails 1 of 5.

not ok 5 - git-compatible commands still work in fixture workspace
# passed: 4   failed: 1

The failing assertion

	(cd ws &&
	 $BIT repo status >../ws-fixture-repo-status.out 2>&1 &&
	 $BIT status >../ws-fixture-implicit-status.out 2>&1
	) &&
	grep "On branch" ws-fixture-repo-status.out &&
	! grep "workspace root:" ws-fixture-repo-status.out &&
	grep "workspace root:" ws-fixture-implicit-status.out

Reproduced by hand on the workspace_flow fixture:

$ bit repo status
On branch main

nothing to commit, working tree clean          # correct: no workspace root line

$ bit status
On branch main
Untracked files:
	dep/
	extra/
	leaf/                                      # expected the workspace status instead

Same three clauses as t9008 test 9, failing on the same one: the implicit-translation gate from #194.

This test is unaffected by #191 — it fails identically before and after that fixture change, which I verified while preparing #192.

Expect it to go green with #194 and no change to this file.

Note

Nothing under t/ runs in CI, which is why this has gone unnoticed. Reproduce with bash t/t9009-workspace-flow-fixture.sh.

[mizchi]

Not a bug — my report was wrong, and I am closing this.

The failure was an artifact of the environment I triaged in. That container exports git config through the environment (GIT_CONFIG_COUNT, GIT_CONFIG_KEY_0..2, GIT_CONFIG_VALUE_0..2, holding credential.interactive and two url.*.insteadOf entries for its proxy).

should_delegate_to_real_git (modules/bit/cmd/bit/main.mbt:1044) treats any GIT_CONFIG_* injection as a reason to hand the command to the real git binary, and it runs before workspace_translate_implicit_command. So bit status never reached the workspace translation — which is the documented intent of that check, not a defect.

With those variables unset the test passes:

$ env -u GIT_CONFIG_COUNT -u GIT_CONFIG_KEY_0 ... bash t/t9009-workspace-flow-fixture.sh
# passed: 5   failed: 0

The hand-run I pasted in the original report was made in the same polluted shell, so it showed the same artifact. Apologies for the noise.

Same correction as #197. #194 and #196 are being updated rather than closed — each still has one genuine failure unrelated to this.

---

Generated by Claude Code