Skip to content

remove: drop all CircleCI support#13

Merged
zuchka merged 1 commit into
mainfrom
remove-circleci-support
May 8, 2026
Merged

remove: drop all CircleCI support#13
zuchka merged 1 commit into
mainfrom
remove-circleci-support

Conversation

@zuchka

@zuchka zuchka commented May 8, 2026

Copy link
Copy Markdown
Collaborator

Summary

Removes CircleCI from DING entirely. No more recipe, no more runctx auto-detection, no more docs mentions.

Files changed: 8 files, +4 / -132 lines.

  • `internal/runctx/runctx.go` — drop the `CIRCLECI=true` detection case
  • `internal/runctx/runctx_test.go` — drop `TestNew_DetectsCircleCI`; remove `CIRCLE_*` from `clearCIEnv`
  • `docs/recipes/circleci.md` — deleted
  • `docs/recipes/index.md` — drop CircleCI row
  • `mkdocs.yml` — drop CircleCI nav entry
  • `README.md` — drop from runner table + CI/CD recipes list
  • `docs/configuration.md` — drop from "Platform-specific examples" pointer
  • `docs/recipes/jenkins.md` — drop "/ CircleCI" reference in a Tradeoffs bullet

Breaking change

Existing users with rules that match `runner=circleci` or rely on CircleCI-derived run-context labels (`repo`, `branch`, `commit`, `job` from CIRCLE_* env) will see those alerts now report `runner=local` instead. This is a feature regression by design.

Background

An attempted Tier-2 CircleCI orb (`ding-labs/ding-circleci-orb`) hit unrecoverable CCI auth/onboarding friction for new GitHub orgs — webhook validation errors, CLI-vs-UI integration mismatches, namespace claim path broken. Rather than ship a half-supported integration, removing CircleCI entirely until the DevOps story improves.

Test plan

  • `go test -race ./...` — full suite green after removal
  • `grep -rn -i "circleci\|CIRCLE" --include=".go" --include=".md" --include=".yml" --include=".yaml" --include="*.example"` — zero remaining mentions in non-superpowers, non-auto-generated files

Post-merge

  • Tag `v0.12.0` (breaking change per established convention).
  • Memory `project_ding_wedge_status.md` — note CircleCI removed; remove the orb-resume-condition framing.
  • External repo `ding-labs/ding-circleci-orb` — pending decision (delete entirely, or leave dormant).

🤖 Generated with Claude Code

Removes CircleCI from DING entirely:

- internal/runctx/runctx.go: drop the CIRCLECI=true detection case;
  removes `circleci` from the package-doc runner list
- internal/runctx/runctx_test.go: drop TestNew_DetectsCircleCI;
  remove CIRCLE_* env vars from clearCIEnv
- docs/recipes/circleci.md: deleted
- docs/recipes/index.md: drop CircleCI status row
- mkdocs.yml: drop CircleCI nav entry
- README.md: drop CircleCI from auto-detection runner table and
  the CI/CD recipes list
- docs/configuration.md: drop CircleCI from "Platform-specific
  examples" pointer
- docs/recipes/jenkins.md: drop "/ CircleCI" reference in a
  Tradeoffs bullet

This is a breaking change for any existing user with rules that
match `runner=circleci` or use CircleCI-derived run-context labels —
those alerts will now report `runner=local` instead.

Background: an attempted Tier-2 CircleCI orb hit unrecoverable CCI
auth/onboarding friction for new GitHub orgs. Rather than ship a
half-supported integration, removing CircleCI entirely until the
DevOps story improves.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@zuchka zuchka merged commit 0ab47ad into main May 8, 2026
1 check passed
@github-actions github-actions Bot locked and limited conversation to collaborators May 8, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant