rename followup: deploy still pinned to coilysiren/eco-spec-tracker #6
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally filed by @coilysiren on 2026-05-09T04:59:34Z - https://github.com/coilysiren/eco-jobs-tracker/issues/10
The 2026-05-08 rename of
eco-spec-tracker->eco-jobs-trackerwas completed at the repo level, butconfig.ymlwas reverted back to the old name because the live deploy is still oncoilysiren/eco-spec-tracker. README documents the asymmetry but does not schedule the cutover.Cited commits:
00f3461- rename: eco-spec-tracker -> eco-jobs-tracker (repo + URLs)4c05460- revert: config.yml name back to coilysiren/eco-spec-tracker (live deploy is on that)f101521- ci: pin GHCR path to pre-rename repo name to match deploy sidecad1b5b- README: document name asymmetryWhy this might matter: an in-flight rename leaves the deploy pipeline with two names for the same thing. Each new contributor has to learn the asymmetry. The CI pin and config revert are both compensations that disappear once the deploy side cuts over.
Keywords: rename eco-spec-tracker eco-jobs-tracker deploy GHCR config.yml
Merged into #2 in the 2026-05-29 backlog burn-down. Rename cutover overlaps deploy bug #2 Reopen if it should stand alone.