add links for status pages

[alexcoderabbitai]

No description provided.

[coderabbitai]

Walkthrough

The documentation in docs/guides/scheduled-reports.md has been updated with an additional instruction under the "Slack/Discord" section. The new text advises users that if the CodeRabbit bot installation fails, they should verify the status pages for Slack or Discord to check for service outages. There are no changes to any exported or public entities.

Changes

File	Change Summary
docs/guides/scheduled-reports.md	Added troubleshooting guidance in the "Slack/Discord" section advising users to check Slack/Discord status pages on installation failure.

Suggested reviewers

• harjotgill

Poem

I'm a bunny with a curious hop,
Leaping through docs on every stop,
I found a clue for installation woes,
Check Slack/Discord if something goes,
Carrots and code—onward we bop!

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[cloudflare-workers-and-pages]

Deploying coderabbit-docs with    Cloudflare Pages

Latest commit:	d20f39b
Status:	✅  Deploy successful!
Preview URL:	https://8c41c149.coderabbit-docs.pages.dev
Branch Preview URL:	https://fix-slack-discord-outage-lin.coderabbit-docs.pages.dev

View logs

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

docs/guides/scheduled-reports.md (1)

132-133: Improve clarity and consistency of status page instructions.

The newly added instruction (line 132) benefits from a slight rewording to enhance readability. Consider adding a comma after "fails" and capitalizing the service names for consistency. This not only improves clarity but also makes the instruction align with common style guidelines for documentation.

-4. If installation fails check the [slack service](https://slack-status.com/) or [discord status](https://discordstatus.com/) page for any outages.
+4. If installation fails, check the [Slack Status Page](https://slack-status.com/) or [Discord Status Page](https://discordstatus.com/) for outages.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2f9fc6d and d20f39b.

📒 Files selected for processing (1)

• docs/guides/scheduled-reports.md (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Cloudflare Pages