kevinveenbirkenbachandClaude Opus 5 123794c7f4 fix(ci-trigger): resolve the run repo through remote.pushDefault ...

A branch with no tracking remote fell straight through to origin, so on a fork checkout every run lookup asked the upstream repository and answered HTTP 404. i8cifail could not reach a single run of this branch.

Consult remote.pushDefault between the tracking remote and origin. That is git's own answer to where the branch is pushed, hence where its runs live, and the i8puma alias already reads exactly this key — the two resolution paths now agree instead of contradicting each other.

The fallback chain had no test at all: every existing case mocks resolve_repo away. Four cases now pin it, including a pushDefault naming a remote that no longer exists.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-10 20:17:07 +02:00

..

administration

fix(ci-trigger): resolve the run repo through remote.pushDefault

2026-08-10 20:17:07 +02:00

build

refactor(lifecycle): single-source the CI-tested lifecycle envelope

2026-07-21 19:08:08 +02:00

console

feat(cli/console): stateful navigation, ls, and modular split

2026-05-22 13:06:38 +02:00

contributing

perf(registry): probe the image mirror before Docker Hub and cache sizes

2026-07-30 17:22:29 +02:00

core

feat(cli): role order tools under meta/roles/order

2026-07-13 01:47:52 +02:00

make

chore(ruff): enable PLE/PLW/PLR/TRY/PYI subset — 121 → 0

2026-05-07 20:22:43 +02:00

meta

refactor(ci): prefix workflows by trigger

2026-08-07 17:05:51 +02:00

__init__.py

…

__main__.py

fix(cli): auto-load .env in the infinito CLI entry-point

2026-05-21 14:55:10 +02:00