Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Stream engineering blog #1178

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Conversation

tyaga001
Copy link

@tyaga001 tyaga001 commented Dec 4, 2024

Summary by CodeRabbit

  • New Features
    • Added a link to the Stream engineering blog under the "S companies" section.
    • Included a link to the 0xADADA blog under the "Individuals/Group Contributors" section.

Copy link

coderabbitai bot commented Dec 4, 2024

Walkthrough

The changes in this pull request involve updates to the README.md file, specifically adding two new entries. A link to the Stream engineering blog has been added under the "S companies" section, and a link to the blog of "0xADADA" has been included in the "Individuals/Group Contributors" section. The overall structure of the document remains unchanged, with these entries integrated into the existing alphabetical listings.

Changes

File Change Summary
README.md Added entry for "Stream" with link to engineering blog; added entry for "0xADADA" with link to their blog.

Poem

In the README, new links shine,
Stream and 0xADADA, oh how fine!
With blogs to share, knowledge to grow,
A hop, a skip, to learn and know! 🐇✨
Let's celebrate this change today,
With joy and cheer, hip-hip-hooray!


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between d312758 and c3f2666.

📒 Files selected for processing (1)
  • README.md (1 hunks)
🧰 Additional context used
🪛 Markdownlint (0.35.0)
README.md

245-245: null
Bare URL used

(MD034, no-bare-urls)

🔇 Additional comments (2)
README.md (2)

245-245: LGTM! Stream entry is correctly placed.

The entry is properly formatted and alphabetically placed in the "S companies" section.

🧰 Tools
🪛 Markdownlint (0.35.0)

245-245: null
Bare URL used

(MD034, no-bare-urls)


Line range hint 379-379: LGTM! 0xADADA entry is correctly placed.

The entry is properly formatted and alphabetically placed in the "# individuals" section.

🧰 Tools
🪛 Markdownlint (0.35.0)

242-242: null
Bare URL used

(MD034, no-bare-urls)


243-243: null
Bare URL used

(MD034, no-bare-urls)


244-244: null
Bare URL used

(MD034, no-bare-urls)


245-245: null
Bare URL used

(MD034, no-bare-urls)


246-246: null
Bare URL used

(MD034, no-bare-urls)


247-247: null
Bare URL used

(MD034, no-bare-urls)


248-248: null
Bare URL used

(MD034, no-bare-urls)


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
🪧 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 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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Outside diff range and nitpick comments (1)
README.md (1)

245-245: Format the URL consistently

The URL should follow the same format as other entries in the list (company name followed by URL).

Apply this diff to fix the formatting:

-* Steam https://getstream.io/blog/topic/engineering/
+* Stream - https://getstream.io/blog/topic/engineering/
🧰 Tools
🪛 Markdownlint (0.35.0)

245-245: null
Bare URL used

(MD034, no-bare-urls)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 50eab27 and d312758.

📒 Files selected for processing (1)
  • README.md (1 hunks)
🧰 Additional context used
🪛 Markdownlint (0.35.0)
README.md

245-245: null
Bare URL used

(MD034, no-bare-urls)

🔇 Additional comments (1)
README.md (1)

Line range hint 391-391: LGTM!

The 0xADADA entry is correctly placed and follows the established format.

🧰 Tools
🪛 Markdownlint (0.35.0)

242-242: null
Bare URL used

(MD034, no-bare-urls)


243-243: null
Bare URL used

(MD034, no-bare-urls)


244-244: null
Bare URL used

(MD034, no-bare-urls)


245-245: null
Bare URL used

(MD034, no-bare-urls)


246-246: null
Bare URL used

(MD034, no-bare-urls)


247-247: null
Bare URL used

(MD034, no-bare-urls)


248-248: null
Bare URL used

(MD034, no-bare-urls)

README.md Outdated Show resolved Hide resolved
@tyaga001
Copy link
Author

tyaga001 commented Dec 4, 2024

@kilimchoi Stream has a high-quality engineering blog focused on scaling real-time chat & feeds.

80%+ content is technical deep-dives into architecture, performance & distributed systems. Good posts on WebSocket scalability, real-time architecture & infrastructure optimization make it valuable for the community. pls review.

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