Hi Tim! I have been following your videos for a very long time now and absolutely love them. Would like to request you to please create a video explaining pytests and how to create assert statements. Of all the teachers online, I find you to be the only one whose content seems relevant and practically useful. I am addicted to your way of teaching. Very grateful to every single one of your videos. Thanks a lot!
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. 👍
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
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?
This is probably the best git tutorial on youtube since it shows you the actual useful intermediate things to know
Hi Tim! I have been following your videos for a very long time now and absolutely love them. Would like to request you to please create a video explaining pytests and how to create assert statements. Of all the teachers online, I find you to be the only one whose content seems relevant and practically useful. I am addicted to your way of teaching. Very grateful to every single one of your videos. Thanks a lot!
Your videos are always on time :')
I needed to get good grip of Git and Github :)
Thanks a lot Tim
Great job on your videos.
Worth noting that the "new" (been a while acutally) to switch (and maybe create) branches is to use `git swich`
Please help me how to run the program in python text
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. 👍
Well explained , thank you bro !
This is video I have looking for!!! Thanks Tim🙏🙏🙏
very nice and easy to understand
Well explained video
Could you cover fast forward vs no fast forward as well and how it relates to merge and main?
Thanks - really useful video. 👌
Thanks, Tim.
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
Would like a Video like this about ci/cd in github action
Thanks
Hey Tim please do more videos on computer vision
Any Comments on gpt 4 and chatgpt plugins?
Best timing as if you knew it 🙂
Use this button to like for more intermediate content🤝
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?
Nice
Bam!
Can I get beginner video link from anyone on this channel
just search from the pleylist of this channel
@@mirshodoripov1035 ok
Why do you code on Windows?
WSL is stronk
First comment🎉
First commit🎉
@@Boss-ks8vt That's a good one! 😂
please someone stop the background music
Bring back tim without beard😢
Thanks