From bf0672a43831bdeb4b93b2d7408cbb3823078763 Mon Sep 17 00:00:00 2001 From: funman300 Date: Tue, 14 Jul 2026 12:11:49 -0700 Subject: [PATCH] Correct the push-auth note: libsecret, not the tea token Pushes authenticate through the global libsecret credential helper. The tea login has auth_method oauth and no token at all, so it cannot create repos or call the API - it was never what authenticated pushes. Co-Authored-By: Claude Opus 4.8 (1M context) --- CLAUDE.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index d79395b..014f574 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -51,9 +51,13 @@ To poke at the engine by hand, copy the stub block from the top of `test.lua`. Balatro Mod Manager. - Crash/load logs: `~/.local/share/Balatro/Mods/lovely/log/` (newest file). - Remote: `https://git.aleshym.co/funman300/JokerComboAdvisor` (private, user's - Gitea). Pushes authenticate via the repo-local credential helper, which - reads the token from `~/.config/tea/config.yml` at push time — never copy - the token into the repo or the remote URL. Commit per feature. + Gitea). `git push` just works: it authenticates through the global libsecret + credential helper (`credential.helper=/usr/lib/git-core/git-credential-libsecret`). + Never copy a token into the repo or the remote URL. Commit per feature. +- The `tea` CLI is installed and logged in as `funman300`, but its stored login has + `auth_method: oauth` and **no token**, so `tea` cannot create repos or call the + API — it is not the thing that authenticates pushes, despite what this file used + to say. Creating a new remote repo needs the web UI (or a token added to `tea`). ## Architecture