test(adr): #795 resolve the own repo in the adr forge tests #804
No reviewers
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.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea!804
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/795-adr-forge-repo-env"
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?
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