fix(t3code): recognize code.m3ta.dev as Gitea for change requests
T3 only detects a Gitea on a custom domain through a matching tea or fj login, so creating a change request failed with "No unknown source control provider is registered". Put tea on T3's PATH with an m3ta-chiron login built at runtime from the hermes-gitea-token agenix secret. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
d25015bc9d
commit
5a66da916d
4 files changed
+38
-1
No files matched your search
@@ -1,6 +1,10 @@
|
||||
{
|
||||
age = {
|
||||
secrets = {
|
||||
hermes-gitea-token = {
|
||||
file = ../../secrets/hermes-gitea-token.age;
|
||||
owner = "m3tam3re";
|
||||
};
|
||||
hermes-env = {
|
||||
file = ../../secrets/hermes-env.age;
|
||||
};
|
||||
|
||||
@@ -22,6 +22,8 @@
|
||||
# - Gitea SSH: m3tam3re's ssh config pins User gitea + key ~/.ssh/gitea
|
||||
# (one-time keygen; pubkey added to the m3ta-chiron account) for
|
||||
# interactive use and git+ssh:// flake inputs. Host key pinned system-wide.
|
||||
# - Gitea change requests: tea with the hermes-gitea-token agenix secret,
|
||||
# baked into the same package.
|
||||
#
|
||||
# One-time interactive steps after deploy (deliberately NOT declarative —
|
||||
# subscription auth must live in each harness's own credential store and
|
||||
|
||||
Reference in new issue
Block a user