283-refactor: refactor RS redirect

[natanchik]

What type of PR is this? (select all that apply)

• 🍕 Feature
• 🐛 Bug Fix
• 🚧 Breaking Change
• 🧑‍💻 Code Refactor
• 📝 Documentation Update

Description

Refactored redirect 'https://rollingscopes.com/' to 'https://rs.school/'. To check if the redirect works:

• follow the link 'https://pr342.rollingscopes.com/community';
• an automatic redirect to 'https://rs.school/' will take place.

Related Tickets & Documents

• Related Issue Fix redirect from 'https://rollingscopes.com/' to 'https://rs.school/' #283

Added/updated tests?

• 👌 Yes
• 🙅‍♂️ No, because they aren't needed
• 🙋‍♂️ No, because I need help

Summary by CodeRabbit

• Chores

  • Updated the production deployment environment to use https://rs.school instead of https://rollingscopes.com.

• Refactor

  • Removed unnecessary redirect logic from rollingscopes.com to rs.school.

[coderabbitai]

Walkthrough

The changes primarily involve updating configuration settings and removing a specific redirection in the application. The configuration change updates the HOST environment variable to point to a new URL, rs.school, from rollingscopes.com. In the application code, the outdated redirection logic that redirected users from rollingscopes.com to the new URL rs.school is removed, ensuring cleaner and more maintainable code.

Changes

Files	Change Summary
.github/workflows/production.yml	Updated HOST environment variable to 'https://rs.school'.
src/app/app.tsx	Removed the redirect logic from rollingscopes.com to rs.school.

Sequence Diagram(s)

(No sequence diagrams needed as the changes are primarily configuration and minor code cleanup.)

Poem

🌐✨ A URL change to brighten the day,
The HOST now points the rs.school way.
Redirects removed, no longer in sight,
Clean, precise, the code feels light.
A tiny tweak, but oh what a boon,
Rolling smoothly to a simpler tune. 🌟🐇

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

[github-actions]

Qodana for JS

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked
☁️ View the detailed Qodana report

Contact Qodana team

Contact us at [email protected]

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 5f4df25 and 1beee56.

Files selected for processing (2)

• .github/workflows/production.yml (1 hunks)
• src/app/app.tsx (1 hunks)

Files skipped from review due to trivial changes (2)

• .github/workflows/production.yml
• src/app/app.tsx

[natanchik]

It doesn't seem to be working.