Skip to content

Commit 7a01378

Browse files
chore: rename the project to munch-manor
The GitHub repository was renamed from foldkit-zombie-game to munch-manor, but the package name, the README title, and the CI secrets stack still used the old name. Rename the root package and its lockfile entry, title the README Munch Manor with the live URL, and point infra/github.ts at the new repository. The secrets were rewritten under the new name, and infra/README.md explains why a rename needs a second, forced deploy of github.ts.
1 parent 13c46e3 commit 7a01378

5 files changed

Lines changed: 7 additions & 5 deletions

File tree

‎README.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
# foldkit-zombie-game
1+
# Munch Manor
22

3-
A pixel-art zombie shooter built with [Foldkit](https://foldkit.dev).
3+
A pixel-art zombie shooter built with [Foldkit](https://foldkit.dev). Play it at https://munch-manor.tanner-scadden.workers.dev.
44

55
The game state lives in one Foldkit Model. Keyboard, mouse, touch, and animation frames arrive as Messages, and a pure `update` advances the game. Zombie spawns come from a seeded random number generator whose state lives in the Model, so the same seed and the same Messages always produce the same game. The scene is drawn with Foldkit's `Canvas` module at 320x180 and scaled up with pixelated rendering.
66

‎bun.lock‎

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

‎infra/README.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,8 @@ To rotate the CI token or change its permissions, edit `github.ts` and run, with
4444
bun alchemy deploy github.ts --stage prod
4545
```
4646

47+
If the repository is renamed, change `REPOSITORY` and deploy twice, the second time with `--force`. The rename makes Alchemy replace each secret: it writes the new one, then deletes the old one, and GitHub redirects the old name to the same repository, so the delete removes the secret just written. The forced deploy writes it again. Check with `gh secret list`.
48+
4749
## Check a deploy
4850

4951
```sh

‎infra/github.ts‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ import * as GitHub from '@alchemy.run/github'
1414
// bun alchemy deploy github.ts --stage prod
1515

1616
const OWNER = 'Tanner-Scadden'
17-
const REPOSITORY = 'foldkit-zombie-game'
17+
const REPOSITORY = 'munch-manor'
1818

1919
// Workers Scripts Write deploys the site. Secrets Store Write lets CI read
2020
// the Cloudflare state store's token, which Alchemy reads back by binding

‎package.json‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
{
2-
"name": "foldkit-zombie-game",
2+
"name": "munch-manor",
33
"license": "MIT",
44
"version": "0.1.0",
55
"type": "module",

0 commit comments

Comments
 (0)