chore: delete the push-to-deploy pipeline nothing consumes #3

Merged

jlxq0 merged 1 commit from chore/remove-dead-pipeline into main

2026-08-26 04:58:05 +00:00

jlxq0 commented

2026-08-26 04:57:57 +00:00

Owner

.forgejo/workflows/docker.yaml built an image, pushed it, and committed a chore(deploy) tag bump back to main. k8s/ declared the lindner-web Deployment that tag was for. That Deployment is not on the cluster, so the third step had nothing to roll out and the first two ran anyway.

It is not dormant. Run #20, 2026-08-24T23:56Z, was triggered by the merge of #2 — the pull request whose entire content was documenting this pipeline as dead. It pushed forge.oddie.app/jlxq0/lindner_web:449d90d and wrote a5afbae, the head commit of this repository.

Measured before deleting

kubectl get deploy -n web returns static-sites 2/2 and nothing else.
The only ArgoCD Application for this site is static-sites, source oddie-apps/static-sites path k8s. Nothing references jlxq0/lindner_web.
www.lindner.earth answers 200 from the anycast edges with the Souin cache header and the edge CSP, neither of which this repository produces.

Decides nothing about #1

If this repository becomes the authoritative copy, the pipeline that replaces this one vendors content into oddie-apps/static-sites rather than building an image. Nothing here survives either answer.

Left in place

Dockerfile and Caddyfile describe an origin nobody builds. Two tests still hold them to the runtime asset allowlist and to a CSP that is not the one serving the site — a green test pinning nothing. Recorded at the top of AGENTS.md; the fix belongs with the decision in #1.

.dockerignore entries for k8s and .forgejo dropped as dead paths.

Reviewed by codex exec --sandbox read-only for surviving references to the deleted paths: none that break.

npm test: 23 passing. npm run check: bundle current.

Refs #1

`.forgejo/workflows/docker.yaml` built an image, pushed it, and committed a `chore(deploy)` tag bump back to `main`. `k8s/` declared the `lindner-web` Deployment that tag was for. That Deployment is not on the cluster, so the third step had nothing to roll out and the first two ran anyway. It is not dormant. Run #20, 2026-08-24T23:56Z, was triggered by the merge of #2 — the pull request whose entire content was documenting this pipeline as dead. It pushed `forge.oddie.app/jlxq0/lindner_web:449d90d` and wrote `a5afbae`, the head commit of this repository. ### Measured before deleting - `kubectl get deploy -n web` returns `static-sites` 2/2 and nothing else. - The only ArgoCD Application for this site is `static-sites`, source `oddie-apps/static-sites` path `k8s`. Nothing references `jlxq0/lindner_web`. - `www.lindner.earth` answers 200 from the anycast edges with the Souin cache header and the edge CSP, neither of which this repository produces. ### Decides nothing about #1 If this repository becomes the authoritative copy, the pipeline that replaces this one vendors content into `oddie-apps/static-sites` rather than building an image. Nothing here survives either answer. ### Left in place `Dockerfile` and `Caddyfile` describe an origin nobody builds. Two tests still hold them to the runtime asset allowlist and to a CSP that is not the one serving the site — a green test pinning nothing. Recorded at the top of `AGENTS.md`; the fix belongs with the decision in #1. `.dockerignore` entries for `k8s` and `.forgejo` dropped as dead paths. Reviewed by `codex exec --sandbox read-only` for surviving references to the deleted paths: none that break. `npm test`: 23 passing. `npm run check`: bundle current. Refs #1

jlxq0 added 1 commit

2026-08-26 04:57:57 +00:00

chore: delete the push-to-deploy pipeline nothing consumes 82ca6fd76e

`.forgejo/workflows/docker.yaml` built an image, pushed it to the registry, and
committed a `chore(deploy)` tag bump back to `main`. `k8s/` declared the
`lindner-web` Deployment that tag was for. That Deployment is not on the cluster
and no ArgoCD Application references this repository, so the third step of the
pipeline had nothing to roll out and the first two ran anyway.

Not dormant. The last run was #20, on 2026-08-24T23:56Z, triggered by the merge
of #2 -- the pull request whose entire content was documenting this pipeline as
dead. It pushed `forge.oddie.app/jlxq0/lindner_web:449d90d` and wrote `a5afbae`,
the head commit of this repository. A warning does not stop a machine that runs.

Measured before deleting:

- `kubectl get deploy -n web` returns `static-sites` 2/2 and nothing else.
- The only ArgoCD Application for this site is `static-sites`, source
  `forge.oddie.app/oddie-apps/static-sites.git` path `k8s`. Nothing references
  `jlxq0/lindner_web`.
- `www.lindner.earth` answers 200 from the anycast edges with the Souin cache
  header and the edge CSP, neither of which this repository produces.

This presupposes nothing about which copy of the site should be authoritative.
If this repository becomes the source, the pipeline that replaces this one
vendors content into `oddie-apps/static-sites` rather than building an image, so
nothing here is worth keeping either way.

`Dockerfile` and `Caddyfile` stay. They describe an origin nobody builds, and
the tests still hold them to the runtime asset allowlist and a CSP that is not
the one serving the site; that is recorded in AGENTS.md rather than fixed here.

npm test: 23 passing. npm run check: bundle current.

Refs #1

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014Pv3j5e5WCepnztyVSEcUJ