alexion
dd58cd9dad
fix(context): tolerate a trailing /api/v1 in the base URL
...
The client (gitea-js) appends /api/v1 to the base URL itself, so a
GITEA_AXI_API_URL that already carries it — a natural guess given the
variable's name — doubled the segment and failed as a spurious
REPO_NOT_FOUND. Normalize the base URL by stripping a trailing /api/v1
(and any trailing slashes) on both the env-URL and tea-login paths, so the
host base and the /api/v1 endpoint both resolve.
2026-07-19 09:41:13 -04:00
..
2026-07-17 22:52:13 -04:00
2026-07-12 09:29:35 -04:00
2026-07-15 10:20:15 -04:00
2026-07-11 19:36:24 -04:00
2026-07-12 20:22:17 -04:00
2026-07-11 09:15:15 -04:00
2026-07-19 09:41:13 -04:00
2026-07-14 11:01:07 -04:00
2026-07-17 10:09:50 -04:00
2026-07-11 07:11:07 -04:00
2026-07-13 22:15:03 -04:00
2026-07-11 07:11:07 -04:00
2026-07-11 20:39:01 -04:00
2026-07-11 21:03:40 -04:00
2026-07-13 19:41:04 -04:00
2026-07-12 09:47:51 -04:00
2026-07-11 20:39:01 -04:00
2026-07-14 12:23:24 -04:00
2026-07-12 19:02:02 -04:00
2026-07-12 09:47:51 -04:00
2026-07-17 10:09:50 -04:00
2026-07-12 19:02:02 -04:00
2026-07-12 09:47:51 -04:00
2026-07-17 18:59:16 -04:00
2026-07-14 07:35:45 -04:00
2026-07-13 22:15:03 -04:00
2026-07-12 20:22:17 -04:00
2026-07-13 19:55:00 -04:00
2026-07-11 21:03:40 -04:00
2026-07-11 21:03:40 -04:00
2026-07-13 22:15:03 -04:00
2026-07-13 19:55:00 -04:00
2026-07-14 12:23:24 -04:00
2026-07-13 20:22:23 -04:00
2026-07-13 19:55:00 -04:00
2026-07-18 16:11:26 -04:00
2026-07-13 20:22:23 -04:00
2026-07-18 16:11:26 -04:00
2026-07-14 12:23:24 -04:00
2026-07-14 11:26:56 -04:00
2026-07-14 11:26:56 -04:00
2026-07-11 07:11:07 -04:00
2026-07-14 11:26:56 -04:00