Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Companion code for the sports vertical: one highlight video per match from a full recording and a list of goals.
edit.mjstrims a 20 second clip at each goal withtrimand joins them withstart: "auto"in one render. A scoreboard computed from the goal list shows the running score per clip, a lower third names the scoring team, and opening and closing cards frame the match. The sample uses the recording from the related guide; the team names and result match the broadcast scoreboard in the footage (Ottoville 1-2 Ottawa Hills).Related guide: https://shotstack.io/learn/automated-sports-highlight-video-api/
Verified: prettier clean; every generated Edit JSON passes
shotstack validate; fresh clone with no key, a wrong key and a badSHOTSTACK_ENVeach print one line and exit 1; a rejected key stops the batch after one line; README claims checked against the code; STANDARDS.md pre-PR checklist run; two-axis Standards/Spec review applied; rendered end to end on stage with the ids below. Musab reviewed all four vertical examples in#gtmon 17 Sep and his points are applied.Stage render (owner m0018rioc2, 18 Sep): ottoville-v-ottawa-hills
3cb027cb-5871-4a13-83b0-0a3344df8ae4, 66 s from the 700 MB source, done about two minutes after submit.The root README bullet will conflict with the sibling vertical PRs; keep all bullets when resolving.
🤖 Generated with Claude Code