test(adr): #795 resolve the own repo in the adr forge tests #804

Merged
hexajon merged 1 commit from fix/795-adr-forge-repo-env into main 2026-10-18 04:52:46 +00:00
Owner

Summary

The forge-tagged reference and decision-issue tests set only MADTEA_URL and MADTEA_TOKEN, so the own-repo resolution found no origin under the push-model forge runner, which ships the committed tree with no .git. Check then failed with "no forge repository detected for this checkout", so the acceptance for the cross-forge issue link and the file-reference check never ran green.

I set MADTEA_USER and MADTEA_REPO from explicit test config, the same way the cross-repo forge test already does, so the check resolves the record's own repo. Test-only; the runner is unchanged. Proven by the full forge suite green on both forges at both pins.

Closes #795

## Summary The forge-tagged reference and decision-issue tests set only MADTEA_URL and MADTEA_TOKEN, so the own-repo resolution found no origin under the push-model forge runner, which ships the committed tree with no .git. Check then failed with "no forge repository detected for this checkout", so the acceptance for the cross-forge issue link and the file-reference check never ran green. I set MADTEA_USER and MADTEA_REPO from explicit test config, the same way the cross-repo forge test already does, so the check resolves the record's own repo. Test-only; the runner is unchanged. Proven by the full forge suite green on both forges at both pins. Closes #795
test(adr): #795 set MADTEA_REPO so the adr forge tests resolve the own repo
Some checks failed
drift / govulncheck (pull_request) Has been skipped
drift / surface-diff (pull_request) Successful in 30s
drift / forgejo-smoke (pull_request) Has been skipped
ci / mcp-conformance (pull_request) Successful in 1m33s
ci / mcp-conformance (push) Successful in -31s
drift / govulncheck (push) Has been skipped
drift / surface-diff (push) Successful in -39s
drift / forgejo-smoke (push) Has been skipped
ci / gate (push) Failing after 2m21s
ci / gate (pull_request) Failing after 9m20s
31693766e2
The forge-tagged reference and decision-issue tests set only MADTEA_URL and
MADTEA_TOKEN, so the own-repo resolution found no origin under the push-model
runner (the tree ships with no .git) and Check failed with "no forge
repository detected for this checkout". Set MADTEA_USER and MADTEA_REPO the
same way the cross-repo forge test already does, so the check resolves the
record's own repo from explicit test config. Test-only; no runner change.
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
sixfold-space/madtea!804
No description provided.