Skip to content

Resolve Slack channel names for factory questions#30

Merged
khaliqgant merged 1 commit into
mainfrom
fix/slack-channel-name-resolution
Jun 22, 2026
Merged

Resolve Slack channel names for factory questions#30
khaliqgant merged 1 commit into
mainfrom
fix/slack-channel-name-resolution

Conversation

@miyaontherelay

@miyaontherelay miyaontherelay commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Allow slack.channel to be configured as a plain channel name, channel ID, mounted channel dir, or /slack/channels/... path
  • Resolve the configured Slack channel against /slack/channels before posting/watching factory dispatch threads
  • Reuse shared Slack channel alias normalization and document accepted config forms

Tests

  • npm test -- src/orchestrator/factory.test.ts -t "mounted channel directory|mid-task agent question|Slack dispatch thread"
  • npm run build
  • npm test
  • npm test -- src/orchestrator/factory.test.ts -t "mounted channel directory"

@gemini-code-assist

Copy link
Copy Markdown

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@coderabbitai

coderabbitai Bot commented Jun 22, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@miyaontherelay, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 49 minutes and 54 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: ee859e82-ed65-4889-8559-01f817279dea

📥 Commits

Reviewing files that changed from the base of the PR and between 431e07a and 493a497.

📒 Files selected for processing (5)
  • README.md
  • src/orchestrator/factory.test.ts
  • src/orchestrator/factory.ts
  • src/writeback/index.ts
  • src/writeback/slack.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/slack-channel-name-resolution

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.

@khaliqgant khaliqgant merged commit 2e01101 into main Jun 22, 2026
3 checks passed
@khaliqgant khaliqgant deleted the fix/slack-channel-name-resolution branch June 22, 2026 13:08
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.

2 participants