docs: update fork history chart to sketch style

[vitali87]

Summary

• Add cache-busting param to fork history SVG URL so GitHub's camo proxy picks up the new sketch style

Test plan

• Verify the fork history chart renders in the sketch (hand-drawn) style on the README

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! 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 focuses on enhancing the visual presentation of the project's fork history. By introducing a version parameter to the SVG URL, it ensures that the updated, sketch-style chart is correctly rendered in the README, bypassing potential caching issues and providing a fresh look.

Highlights

• Documentation Update: Updated the fork history chart in the README to display a new sketch style.
• Cache Busting: Added a cache-busting parameter to the fork history SVG URL to ensure GitHub's camo proxy picks up the updated image.

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 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 counter productive. 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. ↩

[greptile-apps]

Greptile Summary

This PR makes a one-line documentation change: it appends &v=2 as a cache-busting query parameter to the fork history SVG embed URL in README.md, forcing GitHub's camo image proxy to bypass its cached copy and fetch the updated sketch-style chart from fork-history.site.

• Adds &v=2 to the SVG URL: https://fork-history.site/svg?repos=vitali87/code-graph-rag&v=2
• No code, logic, or configuration changes are included.

Confidence Score: 5/5

• This PR is safe to merge — it is a trivial one-line documentation change with no functional impact.
• The change is limited to a single query parameter appended to an image URL in the README. There is no code, logic, configuration, or behaviour affected. The cache-busting approach (&v=2) is a standard and well-understood pattern for bypassing CDN/proxy caches.
• No files require special attention.

Important Files Changed

Filename	Overview
README.md	Adds &v=2 cache-busting query parameter to the fork history SVG URL so GitHub's camo proxy re-fetches the updated sketch-style chart; no other changes.

Sequence Diagram

sequenceDiagram
    participant GitHub as GitHub Renderer
    participant Camo as GitHub Camo Proxy
    participant ForkSite as fork-history.site

    GitHub->>Camo: Request image (old URL, cached)
    Camo-->>GitHub: Return stale SVG (old style)

    Note over GitHub,ForkSite: After adding &v=2 cache-buster

    GitHub->>Camo: Request image (?repos=...&v=2)
    Camo->>ForkSite: Forward new URL (cache miss)
    ForkSite-->>Camo: Return sketch-style SVG
    Camo-->>GitHub: Serve fresh SVG
    GitHub-->>GitHub: Render sketch-style chart in README

Loading

_{Reviews (1): Last reviewed commit: "docs: bust cache for updated fork histor..." | Re-trigger Greptile}

[gemini-code-assist]

Code Review

This pull request updates the fork history chart URL in the README.md file by adding a cache-busting parameter. This is a standard method to ensure GitHub's image proxy fetches the updated chart style. The change is correct and serves its intended purpose. I have no further feedback.

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud