From aee908663319a9e47e45fcc7b962de5945e6af39 Mon Sep 17 00:00:00 2001 From: Michael Czechowski Date: Wed, 25 Feb 2026 19:15:33 +0100 Subject: [PATCH] Fix Gitea pipelines to use authenticated tea CLI without --login flag Remove redundant --login librete flags from all gt-* pipeline tea commands since authentication is already configured via tea logins. This simplifies the commands and prevents potential authentication issues. Co-Authored-By: Claude Sonnet 4.5 --- .wave/pipelines/gt-issue-research.yaml | 4 ++-- .wave/pipelines/gt-issue-rewrite.yaml | 16 ++++++++-------- .wave/pipelines/gt-issue-update.yaml | 8 ++++---- 3 files changed, 14 insertions(+), 14 deletions(-) diff --git a/.wave/pipelines/gt-issue-research.yaml b/.wave/pipelines/gt-issue-research.yaml index e421550..c2bbc50 100644 --- a/.wave/pipelines/gt-issue-research.yaml +++ b/.wave/pipelines/gt-issue-research.yaml @@ -27,7 +27,7 @@ steps: Parse the input to extract the repository and issue number. Use the tea CLI to fetch the issue: - tea issues list --repo --login librete -o json -f index,title,body,labels,state,url --limit 50 + tea issues list --repo -o json -f index,title,body,labels,state,url --limit 50 Then filter the JSON output for the issue matching the requested number. @@ -224,7 +224,7 @@ steps: COMMENT_EOF - tea comment "$(cat /tmp/comment-body.md)" --repo --login librete + tea comment "$(cat /tmp/comment-body.md)" --repo 4. Add a footer to the comment: --- diff --git a/.wave/pipelines/gt-issue-rewrite.yaml b/.wave/pipelines/gt-issue-rewrite.yaml index c7ef281..a0b0a61 100644 --- a/.wave/pipelines/gt-issue-rewrite.yaml +++ b/.wave/pipelines/gt-issue-rewrite.yaml @@ -34,10 +34,10 @@ steps: 1. tea --version 2a. SINGLE ISSUE mode: Parse the repo and number from {{ input }}, then run: - tea issues list --repo --login librete -o json -f index,title,body,labels,url --limit 50 + tea issues list --repo -o json -f index,title,body,labels,url --limit 50 Then filter the JSON for the issue matching the requested number. 2b. BATCH mode: - tea issues list --repo {{ input }} --login librete --limit 10 -o json -f index,title,body,labels,url + tea issues list --repo {{ input }} --limit 10 -o json -f index,title,body,labels,url After getting REAL results from Bash, analyze issues and score them. In single issue mode, analyze the one issue. In batch mode, analyze all returned issues. @@ -74,7 +74,7 @@ steps: The analysis artifact contains poor_quality_issues from the scan step. For EACH issue in poor_quality_issues, use tea CLI to fetch the current body: - tea issues list --repo {{ input }} --login librete -o json -f index,body --limit 50 + tea issues list --repo {{ input }} -o json -f index,body --limit 50 Then filter for the specific issue number. Then create an enhancement plan with: @@ -123,12 +123,12 @@ steps: tea --version Step 2: For EACH issue in the plan, use Bash tool to apply changes: - - If suggested_title differs from current: tea issues edit --repo {{ input }} --login librete -t "suggested_title" - - If body_template is provided: tea issues edit --repo {{ input }} --login librete -d "body_template" - - If suggested_labels: tea issues edit --repo {{ input }} --login librete -L "label1,label2" + - If suggested_title differs from current: tea issues edit --repo {{ input }} -t "suggested_title" + - If body_template is provided: tea issues edit --repo {{ input }} -d "body_template" + - If suggested_labels: tea issues edit --repo {{ input }} -L "label1,label2" Step 3: For each issue, capture the URL from the issue list: - tea issues list --repo {{ input }} --login librete -o json -f index,url --limit 50 + tea issues list --repo {{ input }} -o json -f index,url --limit 50 Then filter for the specific issue number. Step 4: Record the results with fields: enhanced_issues (each with issue_number, @@ -172,7 +172,7 @@ steps: type: prompt source: | For each enhanced issue, verify with: - tea issues list --repo {{ input }} --login librete -o json -f index,title,labels --limit 50 + tea issues list --repo {{ input }} -o json -f index,title,labels --limit 50 Then filter for the specific issue numbers. Compile a verification report with fields: diff --git a/.wave/pipelines/gt-issue-update.yaml b/.wave/pipelines/gt-issue-update.yaml index 420d3f3..e17ef6f 100644 --- a/.wave/pipelines/gt-issue-update.yaml +++ b/.wave/pipelines/gt-issue-update.yaml @@ -35,7 +35,7 @@ steps: 1. tea --version 2. Fetch the full issue: - tea issues list --repo REPO --login librete -o json -f index,title,body,labels,state,url --limit 50 + tea issues list --repo REPO -o json -f index,title,body,labels,state,url --limit 50 Then filter the JSON for the issue matching NUMBER. 3. Get commits since the issue was created (cap at 100): @@ -147,14 +147,14 @@ steps: Step 3: Apply the update: - If title_changed is true: - tea issues edit --repo --login librete -t "" + tea issues edit --repo -t "" - Write the updated_body to a temp file, then apply it: Write updated_body to /tmp/issue-body.md - tea issues edit --repo --login librete -d "$(cat /tmp/issue-body.md)" + tea issues edit --repo -d "$(cat /tmp/issue-body.md)" - Clean up /tmp/issue-body.md after applying. Step 4: Verify the update was applied: - tea issues list --repo --login librete -o json -f index,title,body,url --limit 50 + tea issues list --repo -o json -f index,title,body,url --limit 50 Then filter for the specific issue number. Compare the returned title and body against what was intended. Flag any discrepancies.