[kelos-bot]

What type of PR is this?

/kind bug

What this PR does / why we need it:

kelos get taskspawners previously displayed an empty SOURCE column for TaskSpawners configured with spec.when.webhook (generic webhook), and kelos get taskspawners <name> -d did not print any source information at all. Every other source type (GitHub Issues, GitHub PRs, Jira, Cron, GitHub Webhook, Linear Webhook) had a branch in internal/cli/printer.go, but the generic webhook case was missed.

This PR adds the missing branches in both printTaskSpawnerTable and printTaskSpawnerDetail:

• Table: Generic Webhook (<source>) (e.g. Generic Webhook (sentry)).
• Detail: Source: Generic Webhook plus a Webhook Source: <source> line.

Unit tests cover both new branches.

Which issue(s) this PR is related to:

Fixes #1103

Special notes for your reviewer:

N/A

Does this PR introduce a user-facing change?

Fix `kelos get taskspawners` to display a non-empty SOURCE column for TaskSpawners using the generic webhook source, and include the webhook source identifier in the detail view.

---

Summary by cubic

Fixes CLI output so generic webhook TaskSpawners show their source in table and detail views. Addresses Linear task 1103.

• Bug Fixes
  • Table shows "Generic Webhook ()".
  • Detail view prints "Source: Generic Webhook" and "Webhook Source: ".
  • Tests cover both views and assert these exact strings.

^{Written for commit 8a1ff95. Summary will update on new commits.}

[greptile-apps]

Greptile Summary

This PR adds the missing GenericWebhook branches in printTaskSpawnerTable and printTaskSpawnerDetail, completing coverage for all TaskSpawner source types in the CLI printer. The fix is minimal and consistent with how every other source type is already handled.

• Table view: GenericWebhook now renders as Generic Webhook (<source>), matching the pattern used for GitHubWebhook.
• Detail view: Prints Source: Generic Webhook followed by a Webhook Source: <source> line, consistent with the LinearWebhook and Jira detail blocks.
• Tests: Two new test functions cover both views; the detail assertions use the combined \"Webhook Source: sentry\" string to avoid vacuous substring matches.

Confidence Score: 5/5

Safe to merge — the change is a straightforward two-branch addition with no risk of affecting existing source-type handling.

The implementation slots cleanly into the existing if-else chain, the new branches are inert to all other source types, and the tests cover both the table and detail output paths.

No files require special attention.

Important Files Changed

Filename	Overview
internal/cli/printer.go	Adds GenericWebhook branches to both printTaskSpawnerTable and printTaskSpawnerDetail, consistent with all other source types.
internal/cli/printer_test.go	Adds two new test functions covering the table and detail views for GenericWebhook; the detail test uses the combined "Webhook Source: sentry" string to avoid vacuous matches.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[TaskSpawner.Spec.When] --> B{Source type?}
    B --> C[GitHubIssues]
    B --> D[GitHubPullRequests]
    B --> E[Jira]
    B --> F[Cron]
    B --> G[GitHubWebhook]
    B --> H[LinearWebhook]
    B --> I[GenericWebhook NEW]

    C --> T[Table: workspace/GitHub Issues]
    D --> T2[Table: workspace/GitHub Pull Requests]
    E --> T3[Table: Jira project]
    F --> T4[Table: cron: schedule]
    G --> T5[Table: GitHub Webhook repo]
    H --> T6[Table: Linear Webhook]
    I --> T7[Table: Generic Webhook source]

    T7 --> DV[Detail: Source: Generic Webhook + Webhook Source: source]

Loading

_{Reviews (3): Last reviewed commit: "fix(cli): show source for generic webhoo..." | Re-trigger Greptile}

[cubic-dev-ai]

No issues found across 2 files

[gjkim42]

/kelos pick-up

[kelos-bot]

🤖 Kelos Task Status

Task kelos-pr-responder-issue-comment-a7ef417520c8 has succeeded. ✅

[gjkim42]

/kelos squash-commits

[kelos-bot]

🤖 Kelos Task Status

Task kelos-squash-commits-issue-comment-85066a53c28f has succeeded. ✅

[kelos-bot]

🤖 Kelos Agent @gjkim42

All review feedback was addressed in commit 084782d (combined Webhook Source: sentry label+value into a single substring assertion to avoid the vacuous match against the fixture name). CI is green. Ready for re-review.

[kelos-bot]

Squash complete.

🤖 Kelos Agent @gjkim42

Rebased on origin/main and squashed 2 commits into 1:

• fix(cli): show source for generic webhook taskspawners