fix: add auth headers to curl commands and stack_lock field (#342)
All checks were successful
ci/woodpecker/push/ci Pipeline was successful
ci/woodpecker/pr/ci Pipeline was successful

- Add Authorization header to read-findings curl calls (private Forgejo)
- Add Authorization + Content-Type headers to decompose curl call
- Add stack_lock placeholder to [project] extension section

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Claude 2026-04-07 08:57:39 +00:00
parent da70badb6d
commit ae826f935b

View file

@ -60,6 +60,10 @@ data_flow = "UI → API → backend → data store"
# Example: "GraphQL /graphql, REST /api/v1, RPC ws://localhost:8545" # Example: "GraphQL /graphql, REST /api/v1, RPC ws://localhost:8545"
api_endpoints = "" api_endpoints = ""
# Stack lock configuration (leave empty for default behavior).
# Example: "full" to hold a full stack lock during triage.
stack_lock = ""
# --------------------------------------------------------------------------- # ---------------------------------------------------------------------------
# Steps # Steps
# --------------------------------------------------------------------------- # ---------------------------------------------------------------------------
@ -71,8 +75,10 @@ description = """
Before doing anything else, parse all prior evidence from the issue comments. Before doing anything else, parse all prior evidence from the issue comments.
1. Fetch the issue body and all comments: 1. Fetch the issue body and all comments:
curl -sf "${FORGE_API}/issues/${ISSUE_NUMBER}" | jq -r '.body' curl -sf -H "Authorization: token ${FORGE_TOKEN}" \
curl -sf "${FORGE_API}/issues/${ISSUE_NUMBER}/comments" | jq -r '.[].body' "${FORGE_API}/issues/${ISSUE_NUMBER}" | jq -r '.body'
curl -sf -H "Authorization: token ${FORGE_TOKEN}" \
"${FORGE_API}/issues/${ISSUE_NUMBER}/comments" | jq -r '.[].body'
2. Identify the reproduce-agent comment (look for sections like 2. Identify the reproduce-agent comment (look for sections like
"Reproduction steps", "Logs examined", "What was tried"). "Reproduction steps", "Logs examined", "What was tried").
@ -172,6 +178,8 @@ For each root cause found:
2. Create a backlog issue for each root cause: 2. Create a backlog issue for each root cause:
curl -sf -X POST "${FORGE_API}/issues" \\ curl -sf -X POST "${FORGE_API}/issues" \\
-H "Authorization: token ${FORGE_TOKEN}" \\
-H "Content-Type: application/json" \\
-d '{ -d '{
"title": "fix: <specific description of root cause N>", "title": "fix: <specific description of root cause N>",
"body": "## Root cause\\n<exact code path, file:line>\\n\\n## Fix suggestion\\n<recommended approach>\\n\\n## Context\\nDecomposed from #${ISSUE_NUMBER} (cause N of M)\\n\\n## Dependencies\\n<#X if this depends on another cause being fixed first>", "body": "## Root cause\\n<exact code path, file:line>\\n\\n## Fix suggestion\\n<recommended approach>\\n\\n## Context\\nDecomposed from #${ISSUE_NUMBER} (cause N of M)\\n\\n## Dependencies\\n<#X if this depends on another cause being fixed first>",