ToMotion AI logo
Menu
Back to gallery

Public AI explainer video

Git merge vs git rebase — what's the difference?

Git merge vs git rebase - what's the difference? Okay, so basically, both are used to bring changes from one branch into another. Let's say you're...

Prompt

Source idea used to generate this video.

Create a modern explainer video, vertical 9:16, duration 40-45 seconds. Topic: "Git merge vs git rebase — what's the difference?" VOICEOVER SCRIPT (Use exactly this, with Hinglish tone): "Git merge vs git rebase — what's the difference? Okay, so basically, both are used to bring changes from one branch into another. Let's say you're working on a feature branch, and main has some new changes. Now you're like — 'Okay, ab in changes ko apni branch mein kaise laaun?' You can use git merge or git rebase. With git merge, you're basically saying: 'Let's combine both branches.' Git keeps both histories and creates a merge commit to connect them. Now, git rebase is a little different. You're basically saying: 'Wait, let me take my commits and put them on top of the latest main.' So your commits are replayed on top, giving you a cleaner, linear history. So just remember: Merge → combine the histories. Rebase → put your commits on top. Bas, that's the main difference." VISUAL STYLE: - Theme: Git and GitHub developer theme - Color Palette: GitHub dark mode #0D1117 background, #161B22 cards, Git orange #F05032, white #FFFFFF, green #2EA043 for commits, blue #58A6FF for branches - Use elements like: git branch graphs, commit dots, terminal window, VS Code style UI, GitHub logo, animated arrows - Animation style: Clean, minimal, tech explainer, smooth branch animations - Font: JetBrains Mono or Fira Code for git commands, Inter for text SCENE BREAKDOWN: 1. Show a branching diagram: main and feature branch 2. For MERGE: Show two branches combining with a merge commit, use icon 🔀 3. For REBASE: Show commits being picked and replayed on top of main, linear history, use icon 📌 4. End with split screen comparison: Left = Merge (messy but safe), Right = Rebase (clean linear) IMPORTANT LAYOUT RULE: Leave empty space / no graphics or text in the BOTTOM LEFT CORNER (approx 20% of screen), so I can overlay my small facecam video there. Keep that area clean with just dark background. Add subtle background music - lo-fi coding beats. Add captions in sync.

Narration

Narration used to create this video.

Video narration

Git merge vs git rebase - what's the difference? Okay, so basically, both are used to bring changes from one branch into another. Let's say you're working on a feature branch, and main has some new changes. Now you're like - "Okay, ab in changes ko apni branch mein kaise laaun?" You can use git merge or git rebase. With git merge, you're basically saying: "Let's combine both branches." Git keeps both histories and creates a merge commit to connect them. Now, git rebase is a little different. You're basically saying: "Wait, let me take my commits and put them on top of the latest main." So your commits are replayed on top, giving you a cleaner, linear history. So just remember: Merge → combine the histories. Rebase → put your commits on top. Bas, that's the main difference.