How to Review a Pull Request Like a Senior Developer
Learn how to review a GitHub pull request--where do you look first, when do you wait for their feedback and when do you proceed on your own, and more! 00:00 - Introduction 00:38 - Read the title and description (and issues) 03:11 - Look at the code 04:31 - Look at the commit history 05:08 - Reproduce locally 08:00 - Sending feedback 10:58 - Merge -- but which type? 12:56 - Co-authoring a pull request 13:53 - Conclusion
▶︎
What is a Pull Request, and How Do I Write Great Pull Requests?
▶︎
Cracking Code Review Interview | Complete FAANG Guide From Ex Google
▶︎
How I Use AI to Understand a New Codebase #1
▶︎
3 Git Workflows Every Developer Should Know (And When to Use Each)
▶︎
Git Will Finally Make Sense After This
▶︎
How to Do Code Reviews Like a Human
▶︎
How Senior Developers Review Pull Requests in 2026
▶︎
Pull Request Tips your Team will THANK YOU For (Best Practices)
▶︎
Zig 2026: No-AI Policy, $670K Foundation, Left GitHub & Why Zig Isn’t 1.0 - Andrew Kelley Explains
▶︎
How to make a pull request on an open source project
▶︎
ASMR Addictive Fast Tapping Collection For Deep Sleep & Anxiety Relief (No Talking) — 2.5 Hours
▶︎
Better Code Reviews in 6 SIMPLE STEPS
▶︎
git rebase - Why, When & How to fix conflicts
▶︎
What is a pull request?
▶︎
Git Pull vs Fetch: When To Use Each
▶︎
Git & GitHub Crash Course 2025
▶︎
Creator of C++: Bell Labs, Negative Overhead Abstraction, Mistakes | Bjarne Stroustrup
▶︎
How To REALLY Do Code Reviews
▶︎
🔴 Makkah Live | مكة مباشر | الحرم المكي مباشر | قناة القران الكريم السعودية مباشر | مكه المكرمه
▶︎