feat: enable verbose fetch output from bun

[tcely]

No description provided.

[qodo-code-review]

Review Summary by Qodo

Enable verbose fetch output in bun action

✨ Enhancement

Walkthroughs

Description

• Enable verbose fetch output from bun runtime
• Add BUN_CONFIG_VERBOSE_FETCH environment variable
• Improves debugging visibility for fetch operations

Diagram

flowchart LR
  A["action.yml"] -- "adds BUN_CONFIG_VERBOSE_FETCH env var" --> B["Run Action step"]
  B -- "enables verbose fetch logging" --> C["bun runtime"]

Loading

File Changes

1. action.yml ✨ Enhancement +1/-0

Add verbose fetch environment variable

• Added BUN_CONFIG_VERBOSE_FETCH: 'true' environment variable to the Run Action step
• Enables verbose output for fetch operations in the bun runtime
• Improves debugging and troubleshooting capabilities

action.yml

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (2) 📘 Rule violations (0) 📎 Requirement gaps (0) 🎨 UX Issues (0)

1. Verbose fetch misses installs 🐞 Bug ≡ Correctness

Description

BUN_CONFIG_VERBOSE_FETCH is only set for the "Run Action" step, but the dependency fetches happen
earlier during "Build Binary" (bun install), so verbose fetch output will not be produced for
installs/builds.

Code

action.yml[R81-83]

      env:
+        BUN_CONFIG_VERBOSE_FETCH: 'true'
        INPUT_TOKEN: ${{ inputs.token }}

Evidence

The composite action performs bun install in the Build Binary step without
BUN_CONFIG_VERBOSE_FETCH set, and only enables the env var later when running the already-built
binary.

action.yml[66-75]
action.yml[77-93]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`BUN_CONFIG_VERBOSE_FETCH` is only enabled in the runtime step, so it won’t affect the earlier `bun install` network fetches during the build.

### Issue Context
The composite action runs `bun install` in the "Build Binary" step, then runs the compiled binary in a later step. Step-level `env` applies only to that step.

### Fix Focus Areas
- action.yml[66-75]
- action.yml[77-93]

### Suggested change
Add `BUN_CONFIG_VERBOSE_FETCH: 'true'` to the "Build Binary" step `env:` as well (or export it inside that step’s shell script) if the goal is verbose output for dependency fetching.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. Unconditional verbose log spam 🐞 Bug ✧ Quality

Description

The action now forces verbose fetch logging on every run, and the code performs many GitHub API
operations in loops, which can significantly bloat logs and reduce debuggability (or risk log
truncation).

Code

action.yml[R81-83]

      env:
+        BUN_CONFIG_VERBOSE_FETCH: 'true'
        INPUT_TOKEN: ${{ inputs.token }}

Evidence

BUN_CONFIG_VERBOSE_FETCH is enabled unconditionally for the action execution step, while sweep()
searches issues and repeatedly fetches issue details/timelines and performs write batches—this can
translate into a high number of HTTP calls (and thus verbose fetch lines).

action.yml[77-93]
src/no-response.ts[65-125]
src/no-response.ts[256-322]
src/gh-api-client.ts[36-95]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
Verbose fetch logging is currently forced on for every action run, which can generate very large logs given the action’s repeated GitHub API calls.

### Issue Context
The action already uses `core.debug(...)` for debug-only logs; verbose fetch should typically be gated similarly (e.g., via an input, or via `ACTIONS_STEP_DEBUG`).

### Fix Focus Areas
- action.yml[77-93]
- action.yml[1-34]

### Suggested change
Introduce a new input (e.g., `verboseFetch`, default `false`) and set `BUN_CONFIG_VERBOSE_FETCH` only when that input is true (or when `ACTIONS_STEP_DEBUG == 'true'`). This keeps default logs stable while preserving the ability to enable verbose fetch for troubleshooting.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more