Repository navigation
docs: pull the release before running update.py - #24
Conversation
update.py does not fetch commits; its --pull flag only refreshes the Docker base images. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a1648a7e30
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| ```bash | ||
| cd /srv/scamscreener | ||
| git pull --ff-only origin main |
There was a problem hiding this comment.
Section 7 instructs operators to upload repository contents and never requires /srv/scamscreener to be a Git checkout with an origin remote, so deployments created exactly as documented can fail here with “not a git repository.” When this multi-line block is pasted into an interactive shell, Bash still proceeds to update.py, rebuilding the stale tree and potentially reporting a successful update. Either make the initial installation explicitly clone/configure this repository or retain an upload-based update path and stop execution if release acquisition fails.
AGENTS.md reference: AGENTS.md:L121-L125
Useful? React with 👍 / 👎.
1 participant
scripts/update.pyrebuilds and restarts the checked-out tree; it never fetches commits (--pullonly refreshes Docker base images). Section 14 of DEPLOY.md now shows thegit pull --ff-only origin mainstep beforeupdate.py, which is what the 2026-09-13 deploy needed.🤖 Generated with Claude Code