Skip to content

Remove landing project from README#34

Merged
WomB0ComB0 merged 1 commit into
mainfrom
WomB0ComB0-patch-1
Jul 12, 2026
Merged

Remove landing project from README#34
WomB0ComB0 merged 1 commit into
mainfrom
WomB0ComB0-patch-1

Conversation

@WomB0ComB0

Copy link
Copy Markdown
Member

Removed landing project entry from README.

Summary

Type of change

  • feat — new user-visible capability
  • fix — bug fix
  • docs — documentation only
  • refactor — code change that neither fixes a bug nor adds a feature
  • perf — performance improvement
  • test — adds/updates tests
  • build — build system or external dependency
  • ci — CI configuration
  • chore — other housekeeping
  • Breaking change (! in the commit type)

Test plan

  • [ ]
  • [ ]

Breaking changes

None.

Checklist

  • Commits follow Conventional Commits (commit-msg hook will reject otherwise)
  • Branch name matches the allowed pattern (pre-push hook will reject otherwise)
  • resq pre-commit / resq format --check clean locally
  • New code has tests (or a deliberate note on why not)
  • Docs updated (AGENTS.md / README / inline) for user-visible changes
  • Security-sensitive changes acknowledged (secrets, auth, input validation)

Removed landing project entry from README.

Signed-off-by: Mike Odnis <mike@mikeodnis.dev>
@coderabbitai

coderabbitai Bot commented Jul 12, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@WomB0ComB0, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 56 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 09084868-fece-43cc-9a0e-075551e2df4d

📥 Commits

Reviewing files that changed from the base of the PR and between c061635 and 24bdb5b.

📒 Files selected for processing (1)
  • profile/README.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch WomB0ComB0-patch-1

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

Comment @coderabbitai help to get the list of available commands.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Code Review

This pull request removes the 'landing' repository entry from the list of repositories in the profile README.md. There are no review comments, and I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

@WomB0ComB0
WomB0ComB0 merged commit 0237347 into main Jul 12, 2026
8 checks passed
@WomB0ComB0
WomB0ComB0 deleted the WomB0ComB0-patch-1 branch July 12, 2026 21:40
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