Intermediate GitHub Tutorial

In this video, I’ve teamed up with Microsoft Canada to show how you can use intermediate Git/GitHub features for software development. Specifically, I discuss commands relating avoiding conflicts, fixing mistakes, rebasing vs merging, creating pull requests and using more advanced commands like git cherry-pick and git reset. Special thanks to Microsoft Canada for sponsoring and collaborating on this video!
💻 Register for my Microsoft Developer Digital Meetup Tour webinar on May 9th , 2023, where we’ll discuss advanced developer workflows and you can learn more about VSCode, Git, Github and more!
Git & GitHub For Beginners: • Git Tutorial for Begin...
⭐️ Timestamps ⭐️
00:00 | Intermediate GitHub
01:12 | PRs and Contributions
12:52 | Resolving Conflicts
22:26 | Rebase vs Merge
31:17 | Modifying Existing Remote Branches
35:31 | Cherry Pick and Reset
40:50 | Webinar
◼️◼️◼️◼️◼️◼️◼️◼️◼️◼️◼️◼️◼️◼️
👕 Merchandise: teespring.com/stores/tech-wit...
📸 Instagram: / tech_with_tim
📱 Twitter: / techwithtimm
⭐ Discord: / discord
📝 LinkedIn: / tim-ruscica-82631b179
🌎 Website: techwithtim.net
📂 GitHub: github.com/techwithtim
🔊 Podcast: anchor.fm/tech-with-tim
🎬 My UA-cam Gear: www.techwithtim.net/gear/
💵 One-Time Donations: www.paypal.com/donate?hosted_...
💰 Patreon: / techwithtim
◼️◼️◼️◼️◼️◼️◼️◼️◼️◼️◼️◼️◼️◼️
⭐️ Tags ⭐️
- Tech With Tim
- GitHub
- Intermediate Coding
⭐️ Hashtags ⭐️
#sponsored #techwithtim #github #githubactions #githubtutorial

[@usamashami11]

Your videos are always on time :')
I needed to get good grip of Git and Github :)

[@KayderimGameplays]

Thanks a lot Tim

[@tibzdankan]

This is video I have looking for!!! Thanks Tim🙏🙏🙏

[@yassinegalbi3322]

Well explained , thank you bro !

[@paulthomas1052]

Thanks - really useful video. 👌

[@emman100]

Great video. Forgot to mention git switch or git tag. Also git rebase can be used for a whole lot more but I guess not when working on a public repo. Overall great video. Thanks. 👍

[@bevis2k4]

very nice and easy to understand

[@whonayem01]

Thanks, Tim.

[@gustavojuantorena]

Well explained video

[@farzadmf]

Worth noting that the "new" (been a while acutally) to switch (and maybe create) branches is to use `git swich`

[@Definetlynotplayingminecraft]

Please help me how to run the program in python text

[@DJRanoia]

Could you cover fast forward vs no fast forward as well and how it relates to merge and main?

[@bahibrahim101]

Thanks

[@aram5642]

Merge, by preserving the commits, also preserves the conversations and annotations in a PR, which may be important during the lifetime of a PR. Your collaborators will be able to see what you have solved between commits in response to their comments. Unfortunately git rebase does not provide it. But at the end of a feature branch work and solving all comments, it might be actually beneficial to rebase the branch, as the merge commit might become a large one over time.
When working on a shared branch, one might also want to use git pull --rebase, a very useful command

[@Eswar.]

Hey Tim please do more videos on computer vision

[@ApexGaara]

Would like a Video like this about ci/cd in github action

[@Ismail_Dagli]

Best timing as if you knew it 🙂

[@fatimahmath4819]

Nice

[@jfsaraceno9265]

Bam!

[@parkerwarner8688]

Use this button to like for more intermediate content🤝

[@ajp2206]

Any Comments on gpt 4 and chatgpt plugins?

[@vigneshpadmanabhan]

I have encountered a situation where I was working on a feature branch locally. When I checked out to the main branch and ran 'git status', it showed changes from my feature branch. I tried to do 'git pull' on main but it failed because there were uncommitted changes. Somehow the changes I made in my feature branch also existed in main.
How can I resolve this situation where changes from my feature branch are appearing in main after checking out, even though I haven't merged the branches?
Additionally, I've also faced a situation where running 'git status' shows the same file appearing as both staged and unstaged changes. There were 60+ files that were identical in both staged and unstaged sections. I'm unsure how to determine if the staged version is updated compared to the unstaged one, especially if an automated tool staged the changes as I worked.
How should I approach understanding which version of those duplicate files is correct in cases where 'git status' shows the same file as both staged and unstaged with many duplicates?

[@mrblawblawblaw2335]

Can I get beginner video link from anyone on this channel

[@mirshodoripov1035]

just search from the pleylist of this channel

[@mrblawblawblaw2335]

@@mirshodoripov1035 ok

[@pabloqp7929]

Why do you code on Windows?
WSL is stronk

[@kulture1758]

First comment🎉

[@Boss-ks8vt]

First commit🎉

[@Ismail_Dagli]

​@@Boss-ks8vt That's a good one! 😂

[@itzAustin-qr8zx]

I'm the only who has learnt python but still can't build any thing
Please any one who has suggestion should help me
I have the ideas I just don't know how to build it

[@ayoubMazouz]

keep watching tutorials it will click at some point, I've been there.

[@waffles6555]

Pseudocode on paper 😊

[@RakibHossain-ez8sk]

please someone stop the background music

[@tapiwamotsi1424]

Bring back tim without beard😢

[@sykes257]

Thanks