funman300/JokerComboAdvisor
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Correct the push-auth note: libsecret, not the tea token

Browse Source 
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) <noreply@anthropic.com>
This commit is contained in:
funman300
2026-07-14 12:11:49 -07:00
parent d31b7502ea
commit bf0672a438
1 changed files with 7 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CLAUDE.md
+7 -3
View File
@@ -51,9 +51,13 @@ To poke at the engine by hand, copy the stub block from the top of `test.lua`.
Balatro Mod Manager. Balatro Mod Manager.
- Crash/load logs: `~/.local/share/Balatro/Mods/lovely/log/` (newest file). - Crash/load logs: `~/.local/share/Balatro/Mods/lovely/log/` (newest file).
- Remote: `https://git.aleshym.co/funman300/JokerComboAdvisor` (private, user's - Remote: `https://git.aleshym.co/funman300/JokerComboAdvisor` (private, user's
Gitea). Pushes authenticate via the repo-local credential helper, which Gitea). `git push` just works: it authenticates through the global libsecret
reads the token from `~/.config/tea/config.yml` at push time — never copy credential helper (`credential.helper=/usr/lib/git-core/git-credential-libsecret`).
the token into the repo or the remote URL. Commit per feature. 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 ## Architecture