Remove dead Chaps blog

[pokonski]

It longer exists and isn't coming back

Summary by CodeRabbit

• Documentation
  • Removed the entry for Chaps from the list of companies in the README file.

[coderabbitai]

Walkthrough

The recent update to the project involves a minor modification in the README.md file. Specifically, the entry for the company Chaps has been removed from the list of companies along with their respective URLs. There are no changes to the exported or public entities in the codebase.

Changes

File	Change Summary
README.md	Removed the entry for Chaps from the list of companies with their URLs.

In the README, a change took place,
Chaps' name vanished without a trace. 🐇
A list now shorter, clean and neat,
The project moves with nimble feet.
So onward, code, with grace and cheer,
For updates bring a future clear. ✨

---

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.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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.

[coderabbitai]

Actionable comments posted: 0

Outside diff range and nitpick comments (4)

README.md (4)

Line range hint 3-3: Ensure proper heading levels for better document structure.

-### [Companies](#companies-1)
+## [Companies](#companies-1)

---

Line range hint 6-8: Consider replacing hard tabs with spaces for consistent formatting in markdown files.

---

Line range hint 27-27: Add blank lines around lists for better readability and to adhere to markdown best practices.

---

Line range hint 776-776: Multiple top-level headings detected. Consider restructuring or rephrasing to maintain a single top-level heading.

Also applies to: 780-780, 784-784

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 924f9f6 and 7c7b6f7.

Files selected for processing (1)

• README.md (1 hunks)

Additional Context Used

LanguageTool (5)

README.md (5)

Near line 30: The plural noun “companies” cannot be used with the article “A”. Did you mean “A company” or “companies”?
Context: ... https://99designs.com/tech-blog/ #### A companies * AdRoll http://tech.adroll.com/blog/ *...

---

Near line 188: The pronoun ‘I’ must be used with a non-third-person form of a verb.
Context: ...spot.com/blog/topic/engineering #### I companies * IBM developerWorks https://developer....

---

Near line 428: Use “An” instead of ‘A’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’.
Context: ...ls * 0xADADA https://0xadada.pub/ #### A individuals * Aaron Patterson http://te...

---

Near line 532: Check that the noun ‘individuals’ after the pronoun ‘I’ is correct. It’s possible that you may need to switch to a possessive pronoun, or use another part of speech.
Context: ... Hypriot http://blog.hypriot.com/ #### I individuals * Ian Hummel https://themodernlife.gith...

---

Near line 741: Check that the noun ‘technologies’ after the pronoun ‘I’ is correct. It’s possible that you may need to switch to a possessive pronoun, or use another part of speech.
Context: ...ies * Go https://blog.golang.org/ #### I technologies * IPFS https://ipfs.io/blog/ #### J te...