docs: regenerate README demo assets with the 2.0.0 tool + fix broken links#12
Conversation
…links The README 'Example Output' click-through links pointed at CTMobi/.../releases/latest/download/*.mp4, but our v2.0.0 release had no assets (PR #8 repointed them from upstream's kdowswell release to ours without re-hosting the videos), so all 6 download links 404'd. Regenerated the demo media with the 2.0.0 tool itself: - Hero loop: /veo single-shot (720p/4s, audio off — hero-background default) + seamless loop via the video-loop skill. - 4-shot 'Dataflow launch': /veo-multi-shot (fast 1080p/8s, audio on — the new context-aware audio default for the marketing use case), assembled with ffmpeg. - Fresh thumbnails (1280px) extracted from the new clips. Uploaded the 6 MP4s as assets to the v2.0.0 release and pinned the README links to the immutable tag (/releases/download/v2.0.0/) instead of /latest/. All 6 download URLs verified 200. Generated live on Vertex AI (project claude-ve). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (6)
📒 Files selected for processing (1)
📝 WalkthroughSummary by CodeRabbitNote di rilascio
WalkthroughIn ChangesAggiornamento URL video nel README
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
|
Claude finished @GiuseppeIuculano's task in 1m 25s —— View job Review — PR #12 · Rigenerazione asset demo README
✅ Approvo nel merito. È una PR di sola documentazione, minimale (4 righe modificate in Cosa ho verificato
Osservazioni (nessun blocco)
Nel complesso: pulito, mirato, mergeabile. 👍 |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates several asset download links in the README.md file to point to a specific release version (v2.0.0) instead of the generic 'latest' release. 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.
There was a problem hiding this comment.
Pull request overview
Updates README demo video links to stop 404s by pointing the “Example Output” thumbnails at the v2.0.0 release assets (immutable tag URL) instead of releases/latest, aligning the documentation with where the MP4s are actually hosted.
Changes:
- Repointed all README “Example Output” MP4 links from
/releases/latest/download/…to/releases/download/v2.0.0/…. - Kept thumbnail references intact (verified
docs/thumbnails/*files exist).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Up to standards ✅🟢 Issues
|
![codacy-production[bot]](https://avatars.githubusercontent.com/in/56611?s=60&v=4){kind=small}
There was a problem hiding this comment.
Pull Request Overview
The PR successfully addresses the issue of broken links by pinning several README assets to the v2.0.0 release tag. Codacy analysis indicates the changes are up to standards with no new quality issues. However, there is an implementation gap regarding the acceptance criteria for thumbnail updates: specifically, 'multi-shot-assembled.jpg' was not modified despite the regeneration of its associated video. Additionally, while the multi-shot video link was pinned to a release asset, other demo links remain pointed at potentially ephemeral external URLs, which may lead to future link rot.
Test suggestions
- Verify that all video download URLs in the README point to the v2.0.0 release and resolve correctly.
- Verify that thumbnail image paths referenced in the README correspond to existing files in the 'docs/thumbnails/' directory.
TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback
| A seamless looping abstract background for website hero sections. | ||
|
|
||
| [](https://github.com/CTMobi/veo-tools/releases/latest/download/hero-loop.mp4) | ||
| [](https://github.com/CTMobi/veo-tools/releases/download/v2.0.0/hero-loop.mp4) |
There was a problem hiding this comment.
🟡 MEDIUM RISK
Suggestion: The links on lines 13, 30, and 34 use external URLs which may be temporary. To prevent future 'broken links' and ensure the immutability intended by this PR, consider hosting these regenerated assets as attachments in the GitHub Release, following the pattern used for the multi-shot video on line 21.
Problem
The README Example Output click-through links pointed at
CTMobi/veo-tools/releases/latest/download/*.mp4, but ourv2.0.0release had no assets — PR #8's "CTMobi everywhere" change repointed them from upstream'skdowswellrelease (which hosts the MP4s) to ours, without re-hosting the videos. All 6 download links 404'd. (The thumbnails themselves were fine — they're committed.)Fix — regenerated the demos with the 2.0.0 tool itself
/veosingle-shot,hero-backgrounduse case → 720p/4s, audio off (the context-aware default for hero), then seamless loop via thevideo-loopskill./veo-multi-shot,marketinguse case → fast 1080p/8s, audio on (showcases the new 2.0.0 context-aware audio default), assembled with ffmpeg (32s).Uploaded the 6 MP4s as assets to the v2.0.0 release and pinned the README links to the immutable tag (
/releases/download/v2.0.0/) instead of/latest/, so they won't drift.Verification
…/releases/download/v2.0.0/*.mp4URLs return 200.docs/thumbnails/.npx tsc --noEmitclean ·npx vitest run219/219 (no code touched).claude-ve); total ~$21.20 as approved.Note: the fast endpoint was intermittently overloaded during generation; an auto-retry-with-backoff loop caught the recovery windows. No charge for failed attempts.
🤖 Generated with Claude Code