docs: fix Workspace schema and deprecated bodyContains in example 10

Merged
KE
5mo ago
+5-6

What type of PR is this?

/kind docs

What this PR does / why we need it:

examples/10-taskspawner-github-webhook/taskspawner.yaml had two bugs that would trip up a new user following the example end-to-end:

  1. The Workspace appended at the bottom used the object form spec.repo.url, but WorkspaceSpec.Repo is typed as a plain string (api/v1alpha1/workspace_types.go). Kubernetes admission would reject the manifest. Every other workspace example in the repo uses the correct string form — this PR brings example 10 in line.
  2. The issue_comment filter used bodyContains: "/kelos". bodyContains is marked Deprecated in api/v1alpha1/taskspawner_types.go and in docs/reference.md; bodyPattern is the supported replacement. Following the deprecated example silently teaches new users to write deprecated configs.

The same bodyContains usage appeared in the GitHub Webhook example in docs/integration.md (and in its trailing "Filtering options" sentence). Both are switched to bodyPattern so the docs and the example stay consistent.

Which issue(s) this PR is related to:

Fixes #1118

Special notes for your reviewer:

Docs / example YAML only — no code or CRD changes. /kelos is a literal prefix and is also a valid regex (no special characters), so swapping bodyContains → bodyPattern preserves the example's intent.

Does this PR introduce a user-facing change?

NONE

Summary by cubic

Fixes example 10 by correcting the Workspace schema (spec.repo is a string) and switching the GitHub webhook filter from deprecated bodyContains to bodyPattern. Prevents Kubernetes admission rejections and keeps the example on supported filters.