Update README.md

[omiaydin1]

Purpose or design rationale of this PR

Describe your change. Make sure to answer these three questions: What does this PR do? Why does it do it? How does it do it?

PR title

Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

• build: Changes that affect the build system or external dependencies (example scopes: yarn, eslint, typescript)
• ci: Changes to our CI configuration files and scripts (example scopes: vercel, github, cypress)
• docs: Documentation-only changes
• feat: A new feature
• fix: A bug fix
• perf: A code change that improves performance
• refactor: A code change that doesn't fix a bug, or add a feature, or improves performance
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
• test: Adding missing tests or correcting existing tests

Deployment tag versioning

Has tag in common/version.go been updated or have you added bump-version label to this PR?

• No, this PR doesn't involve a new deployment, git tag, docker image tag
• Yes

Breaking change label

Does this PR have the breaking-change label?

• No, this PR is not a breaking change
• Yes

Summary by CodeRabbit

• Style
  • Updated README formatting with a leading blank line.

[coderabbitai]

📝 Walkthrough

Walkthrough

A blank line was added at the top of README.md before the main header. This is a formatting-only change with no modifications to documentation content or functionality.

Changes

Cohort / File(s)	Summary
README formatting README.md	Added leading blank line at the beginning of file before main header.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Poem

A newline sits at the top so neat,
A blank space makes the README complete,
One line of whitespace, simple and true,
A rabbit approves this formatting too! 🐰✨

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is incomplete; the 'Purpose or design rationale' section was not filled out, and no conventional commit type was selected from the checklist.	Complete the 'Purpose or design rationale' section explaining the change and select an appropriate conventional commit type (likely 'docs') in the PR title section.
Title check	❓ Inconclusive	The title 'Update README.md' is vague and generic, using non-descriptive language that doesn't convey the specific nature of the change (adding a blank line).	Follow conventional commits format with a specific type prefix (e.g., 'docs: add leading blank line to README.md') to better describe the change.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

No actionable comments were generated in the recent review. 🎉

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}