Claude/update prod runner script lq2g s - #62
Conversation
- Add tipsStore with 15 default sweepstakes-safe tips (id, text, enabled)
- Add TIPS_GROUP constant (@GambleCodezPrizeHub, overridable via env)
- Persist tipsStore in runtime-state.json (snapshot + load)
- Start tips scheduler on bot launch: posts one random enabled tip
silently every 4 hours to @GambleCodezPrizeHub (disable_notification)
- Scheduler is re-armable when admin changes the interval
Admin commands:
/tips /t /tp — Tips Manager dashboard with inline buttons
/tiplist — Show all tips with IDs and preview
/tipadd — Prompt for new tip text (state: await_tip_add_text)
/tipremove — Select tip by button to delete
/tipedit — Select tip by button then prompt for new text
/tiptoggle — Toggle entire tips system on/off
/tiptest — Send one random tip preview to admin in DM
/tipsettings — Show settings and update interval (hours)
Inline button actions:
tips_cmd_{add,edit,remove,toggle,list,test,settings}
tip_remove_<id> — remove a specific tip
tip_edit_select_<id> — prompt to edit a specific tip
tip_toggle_<id> — enable/disable individual tip
pendingAction state machine:
await_tip_add_text → save new tip, reply "Added as Tip #X"
await_tip_edit_text → update tip text, reply "Tip #X updated"
await_tip_settings_interval → update interval + restart scheduler
https://claude.ai/code/session_01X3PxGFF5zzKptQwVkjYzzN
GitHub CI:
- deploy.yml: disable `deploy` job with `if: false` — GitHub Actions
must NEVER restart or launch the bot; it is code storage only.
Quality-gates job (syntax, tests, audit) continues to run on push.
- ci.yml: unchanged — already runs tests without touching Telegram.
index.js runtime guards (layered):
- CI / smoke-test layer: if CI=true or DISABLE_RUNTIME=1 → log and
skip all runtime startup without calling process.exit() so that
`require('./index.js')` in smoke tests completes cleanly.
- VPS-only layer: if DEVICE !== "vps" → print warning and exit(0).
Set DEVICE=vps in the VPS .env to allow the bot to start.
/deploy admin command:
- Restart logic is systemctl-only (no PM2); unchanged from original.
deploy.sh (new, VPS-only):
- git fetch --all && git reset --hard origin/main
- npm ci --omit=dev
- systemctl restart runewager
- systemctl is-active confirmation
.env.example:
- Added DEVICE=vps entry so prod-run.sh copies it correctly.
https://claude.ai/code/session_01X3PxGFF5zzKptQwVkjYzzN
…scripts - /deploy Telegram command: git pull -> git fetch --all + git reset --hard origin/main + git clean -fd. Prevents hangs caused by dirty working trees, untracked files, or merge conflicts that made /deploy stuck. - prod-run.sh: same fetch+reset change for the initial code-pull step. - deploy.sh: add systemctl stop before git ops (prevents file locks during reset) and git clean -fd after reset (removes stale untracked files). All three paths now use the same hard-reset strategy. Systemd service, CI guard (CI=true/DISABLE_RUNTIME=1), and DEVICE=vps guard are unchanged as they were already correct. https://claude.ai/code/session_01X3PxGFF5zzKptQwVkjYzzN
|
CodeAnt AI is reviewing your PR. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Caution Review failedThe pull request is closed. 📝 WalkthroughWalkthroughThree deployment-related files are updated to replace Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
Note 🎁 Summarized by CodeRabbit FreeYour organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login. Comment |
GitHub Actions
Inactive
GitHub Actions
Error
This reverts commit 5168fb7.
GitHub Actions
Inactive
GitHub Actions
Error
codeant-ai
Bot
added
the
size:S
Nitpicks 🔍
|
|
CodeAnt AI finished reviewing your PR. |
2 participants
CodeAnt-AI Description
Update deployment flow to use fetch+hard-reset, clean untracked files, and stop service before updating
What Changed
Impact
✅ Fewer deploy failures due to dirty working trees✅ Fewer file-lock errors during updates✅ Cleaner working tree after deploy (untracked files removed)💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.
Summary by CodeRabbit