bug(forge-test): the adr live forge test fails under the push-model runner, which ships no .git #795
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#530 adr check: resolve cross-repo record links, so an impacts pair cannot go one-way or dangle
sixfold-space/madtea
#632 adr check: C11 drops the host from an issue URL and reads the link on the record's own forge
sixfold-space/madtea
#658 adr check: verify every file reference in a record
sixfold-space/madtea
Reference
sixfold-space/madtea#795
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What happens
scripts/forge-vm/run-forge-tests.sh pushes the committed tree into the VM with
git archive HEAD, which ships tracked files only and no.git. The adr live forge test then has no checkout with an origin to resolve.Running the forge-tagged suite over internal/service/adr fails:
The runner also warns the pushed tree has no git identity (user.name "" in git vs "forgetest" in the forge).
Why it matters
The live forge test is the acceptance proof for the cross-forge decision-issue link (#632) and the file-reference check (#658). Both landed on main, but their live-forge acceptance cannot run green through the committed runner, so neither closes on a real forge run.
Possible directions
Relates to #677, #678, #693.