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

chore(docs): update readme to use banner rather than logo #106

Merged
merged 2 commits into from
May 25, 2024

Conversation

madflojo
Copy link
Member

@madflojo madflojo commented May 25, 2024

The way the logo renders doesn't sit right with me, I think it would be better to use the full banner.

Summary by CodeRabbit

  • Documentation
    • Updated README to replace the tarmac logo with a tarmac banner image.

Copy link
Contributor

coderabbitai bot commented May 25, 2024

Warning

Rate Limit Exceeded

@madflojo has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 35 minutes and 5 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.
Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.
Please see our FAQ for further information.

Commits Files that changed from the base of the PR and between e6c2200 and 0c50ff8.

Walkthrough

The recent update involves a visual enhancement to the documentation by replacing the tarmac logo with a more prominent tarmac banner image. This change aims to improve the aesthetic appeal and clarity of the README.

Changes

File Change Summary
docs/README.md Replaced tarmac-logo.png with tarmac-banner.png

🐰 In the world of code, a banner unfurled,
To make the README shine, a new image swirled.
The tarmac's tale, now better told,
With a banner bright, a sight to behold.
Hoppity hop, the changes we sing,
For a README that’s fit for a king! 🌟


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

Copy link
Contributor

@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 (2)
docs/README.md (2)

Line range hint 13-13: Correct the spelling to include a hyphen: "language-agnostic".

- Tarmac is language agnostic and offers built-in support for key/value stores like BoltDB, Redis, and Cassandra...
+ Tarmac is language-agnostic and offers built-in support for key/value stores like BoltDB, Redis, and Cassandra...

Line range hint 79-94: Standardize the use of dollar signs in command examples.

Consider removing the dollar signs before commands in the example sections to maintain consistency and avoid confusion when copying and pasting commands.

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between 048d2ae and e6c2200.
Files ignored due to path filters (1)
  • docs/tarmac-banner.png is excluded by !**/*.png
Files selected for processing (1)
  • docs/README.md (1 hunks)
Additional Context Used
LanguageTool (1)
docs/README.md (1)

Near line 13: This expression is ususally spelled with a hyphen
Context: ...ch to application frameworks. Tarmac is language agnostic and offers built-in support for key/val...
Rule ID: SPECIFIC_HYPHEN

Markdownlint (35)
docs/README.md (35)

27: Column: 1
Hard tabs


28: Column: 1
Hard tabs


34: Column: 1
Hard tabs


36: Column: 1
Hard tabs


37: Column: 1
Hard tabs


38: Column: 1
Hard tabs


39: Column: 1
Hard tabs


40: Column: 1
Hard tabs


46: Column: 1
Hard tabs


48: Column: 1
Hard tabs


49: Column: 1
Hard tabs


51: Column: 1
Hard tabs


52: Column: 1
Hard tabs


53: Column: 1
Hard tabs


54: Column: 1
Hard tabs


55: Column: 1
Hard tabs


56: Column: 1
Hard tabs


57: Column: 1
Hard tabs


58: Column: 1
Hard tabs


59: Column: 1
Hard tabs


60: Column: 1
Hard tabs


61: Column: 1
Hard tabs


63: Column: 1
Hard tabs


64: Column: 1
Hard tabs


65: Column: 1
Hard tabs


66: Column: 1
Hard tabs


67: Column: 1
Hard tabs


68: Column: 1
Hard tabs


69: Column: 1
Hard tabs


71: Column: 1
Hard tabs


72: Column: 1
Hard tabs


79: null
Dollar signs used before commands without showing output


80: null
Dollar signs used before commands without showing output


94: null
Dollar signs used before commands without showing output


3: null
Images should have alternate text (alt text)

docs/README.md Outdated Show resolved Hide resolved
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
@madflojo madflojo merged commit 3883ee9 into tarmac-project:main May 25, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant