Skip to content

docs(fork-changes): backfill all six TBD hashes - #375

Merged
jphein merged 1 commit into
mainfrom
docs/backfill-tbd-hashes
Jul 4, 2026
Merged

docs(fork-changes): backfill all six TBD hashes#375
jphein merged 1 commit into
mainfrom
docs/backfill-tbd-hashes

Conversation

@jphein

@jphein jphein commented Jul 4, 2026

Copy link
Copy Markdown
Collaborator

Resolves every commit: TBD in the manifest to its real squash hash (verified via git log --grep per entry) + regenerated render targets. check-docs 7/7 clean. Closes #371.

🤖 Generated with Claude Code

be903e6 (depth cache), b46f18d (sync 368), 8711e1c (sync 350),
42a107b (concurrent mining), 373fdf2 (sync 340), 8e0d896 (auto_wake).
check-docs clean — every hash now resolves.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings July 4, 2026 15:40

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@coderabbitai

coderabbitai Bot commented Jul 4, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 9 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 Plus

Run ID: 63f64a56-decd-4a55-8665-18a88c7eb2a1

📥 Commits

Reviewing files that changed from the base of the PR and between f284778 and 6055158.

📒 Files selected for processing (4)
  • FORK_CHANGELOG.md
  • README.md
  • docs/fork-changes.yaml
  • website/public/llms-full.txt
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/backfill-tbd-hashes

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.

@jphein
jphein merged commit ebfcf0f into main Jul 4, 2026
16 checks passed
@jphein
jphein deleted the docs/backfill-tbd-hashes branch July 4, 2026 15:46
@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request cleans up the project documentation by resolving placeholder commit hashes. By backfilling these values with verified git hashes, the documentation now provides accurate references for the listed fork-ahead changes, improving traceability for developers and reviewers.

Highlights

  • Documentation Update: Replaced all six 'TBD' commit hashes in the project documentation with their verified squash hashes.
  • Consistency: Updated both the README.md and the internal documentation files to ensure all fork-ahead changes are correctly linked to their respective commits.
Ignored Files
  • Ignored by pattern: FORK_CHANGELOG.md (1)
    • FORK_CHANGELOG.md
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

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

Copy link
Copy Markdown

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 updates the documentation across README.md, docs/fork-changes.yaml, and website/public/llms-full.txt by replacing placeholder 'TBD' commit hashes with the actual Git commit hashes for several fork-ahead changes and upstream syncs. I have no feedback to provide as there are no review comments.

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.

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.

docs: backfill three TBD commit hashes in fork-changes.yaml

2 participants