Skip to content

Add channel management commands for triage#14

Merged
frostebite merged 11 commits intomainfrom
feat/channel-management-commands
Mar 29, 2026
Merged

Add channel management commands for triage#14
frostebite merged 11 commits intomainfrom
feat/channel-management-commands

Conversation

@frostebite
Copy link
Copy Markdown
Member

Summary

  • !channel list <guild> — View detailed channel config (type, monitor, threads, prompt)
  • !channel set <guild> <channel> <key> <value> — Update channel properties (monitor, read_threads, channel_type, reply_mode, system_prompt)
  • !channel add <guild> <channel> [text|forum] — Add a new monitored channel
  • !channel remove <guild> <channel> — Remove a channel from config

All changes are:

  1. Saved to config.json
  2. Applied to in-memory guild mappings immediately
  3. Committed and pushed to main to persist and trigger deploy

Also adds reloadConfig() and saveConfig() to src/config.ts.

Test plan

  • !channel list game-ci shows all channels with properties
  • !channel set game-ci general monitor false disables monitoring, pushes to main
  • !channel set game-ci general monitor true re-enables it
  • !channel add game-ci-develop test-channel adds a new channel entry
  • !channel remove game-ci-develop test-channel removes it
  • After each set/add/remove, git log shows the new commit on main

🤖 Generated with Claude Code

frostebite and others added 11 commits March 28, 2026 22:56
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
New triage commands to view and update channel configurations:
- !channel list <guild> — Show detailed channel config
- !channel set <guild> <channel> <key> <value> — Update a property
- !channel add <guild> <channel> [text|forum] — Add a new channel
- !channel remove <guild> <channel> — Remove a channel

Changes are saved to config.json, committed, and pushed to main
to persist and trigger auto-deploy.

Also adds reloadConfig() and saveConfig() to config.ts.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 29, 2026

Warning

Rate limit exceeded

@frostebite has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 11 minutes and 49 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 11 minutes and 49 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 0e92ee0c-5b40-4ed3-9e07-3cda494a3516

📥 Commits

Reviewing files that changed from the base of the PR and between 223bda1 and b5e0649.

📒 Files selected for processing (2)
  • src/config.ts
  • src/core/live.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/channel-management-commands

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@frostebite frostebite merged commit 69ba163 into main Mar 29, 2026
2 checks passed
@frostebite frostebite deleted the feat/channel-management-commands branch March 29, 2026 01:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant