Auto-update: broke brings in the newest version each time it starts
On start, broke fetches main and fast-forwards when this copy has no changes of its own, then reinstalls only if package-lock.json changed. With your own changes it says to run npm run update; offline, no git or BROKE_NO_AUTO_UPDATE=1, it starts the copy you have. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
19e093451d
commit
3a4b6a0371
2 files changed
+22
-2
No files matched your search
@@ -45,7 +45,7 @@ cd ~/broke && claude
|
||||
|
||||
`CLAUDE.md` tells it the privacy rules. Run `npm run dev` to see changes as they happen. On an online copy, `git push` publishes them.
|
||||
|
||||
**Get the latest broke:** run `npm run update`. On an online copy there's nothing to install: in your GitHub repo open Actions, Update broke, Run workflow, and Vercel rebuilds your site. Your changes stay either way.
|
||||
**Get the latest broke:** it updates itself each time you start it (`broke`, or the install command), as long as you haven't changed its code. With your own changes, run `npm run update`. To turn auto-update off, start it with `BROKE_NO_AUTO_UPDATE=1`. On an online copy there's nothing to install: in your GitHub repo open Actions, Update broke, Run workflow, and Vercel rebuilds your site. Your changes stay either way.
|
||||
|
||||
If you make something others would want, send a pull request.
|
||||
|
||||
|
||||
Reference in new issue
Block a user