From afd73e26de544c5781d895bc452a71bef623bdfa Mon Sep 17 00:00:00 2001
From: Ryan Hamamura <58859899+ryanhamamura@users.noreply.github.com>
Date: Fri, 20 Feb 2026 17:05:48 -1000
Subject: [PATCH] fix: add explicit --login and --repo flags to tea commands

---
 .claude/commands/pr.md      | 4 ++--
 .claude/commands/release.md | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/.claude/commands/pr.md b/.claude/commands/pr.md
index b0f5067..b56391d 100644
--- a/.claude/commands/pr.md
+++ b/.claude/commands/pr.md
@@ -5,9 +5,9 @@ Create a PR on Gitea, wait for CI, and squash-merge it. Push code to both remote
 3. Fetch latest main and rebase: `git fetch gitea main && git rebase gitea/main`.
    - If conflicts occur, abort the rebase (`git rebase --abort`), analyze the conflicting files, write a plan to resolve them, and present the plan to the user before proceeding.
 4. Push the branch to both remotes: `git push -u gitea <branch> && git push origin <branch>` (use `--force-with-lease` if already pushed).
-5. Create a Gitea PR: `tea pr create --head <branch> --base main`. Reference related issues with `#X`. Only use `Closes #X` if the PR fully resolves the issue.
+5. Create a Gitea PR: `tea pr create --login gitea --repo ryan/via --head <branch> --base main`. Reference related issues with `#X`. Only use `Closes #X` if the PR fully resolves the issue.
 6. Wait for CI to pass: poll Gitea CI status. If CI fails, report the failure and stop — do not merge.
-7. Once CI passes, squash-merge on Gitea: `tea pr merge <index> --style squash` with a clean, semantic commit message including the PR number. No Claude attribution lines.
+7. Once CI passes, squash-merge on Gitea: `tea pr merge --login gitea --repo ryan/via <index> --style squash` with a clean, semantic commit message including the PR number. No Claude attribution lines.
 8. Update local main and push to both remotes. If in a worktree, `main` is checked out in the primary tree, so run from there: `cd <primary-worktree> && git pull gitea main && git push origin main` (the primary worktree path is the repo root without `.claude/worktrees/…`). If not in a worktree: `git checkout main && git pull gitea main && git push origin main`.
 9. Clean up remote branches: `git push gitea --delete <branch> && git push origin --delete <branch>`.
 10. Prune refs: `git remote prune gitea && git remote prune origin`.
diff --git a/.claude/commands/release.md b/.claude/commands/release.md
index a9f7cba..b88fdc4 100644
--- a/.claude/commands/release.md
+++ b/.claude/commands/release.md
@@ -16,5 +16,5 @@ Create a new release on Gitea. Push tags to both remotes.
    Present the proposed version, bump rationale, and commit list. Wait for user approval.
 6. Tag the new version. Push the tag to both remotes: `git push gitea <tag> && git push origin <tag>`.
 7. Generate release notes grouped by type (features, fixes, chores).
-8. Create a Gitea release with `tea releases create` using the notes.
+8. Create a Gitea release with `tea releases create --login gitea --repo ryan/via` using the notes.
 9. Report the release URL and confirm all remotes are up to date.