Git Flow Part 1 - What is Git Flow
ฝัง
- เผยแพร่เมื่อ 9 เม.ย. 2016
- I take you through exactly what Git Flow is and how to apply it to a team. This video serves as a strong foundation for you. You should take what you learn from this video, assess it first, then apply it to you project...
1 - What is Git Flow - 0:06
2 - How it works - 0:35
3 - Creating a feature - 2:29
4 - Release Branches - 5:32
5 - Managing Hotfixes - 10:52
☕️ You can buy me a coffee by supporting this video on Patreon:
/ revalgovender
😊You can find me here:
LinkedIn: / reval-govender-0ba14860
Twitter: / revalgovender
Links:
Atlassian - www.atlassian.com/git/tutoria...
Vince Driessen - nvie.com/posts/a-successful-gi...
Semantic Versioning - semver.org/
/**UPDATE **/
Scenario: You need to make a "hotfix", after you have already created a "release branch".
Solution:
1. You should create your "hotfix" branch as described at: 10:52
2. Once you have completed your "hotfix", you should merge it back into "develop" and "master", as described in the video.
3. You also need to merge your "hotfix" branch into your "release" branch. This is to ensure your release branch has the latest stable code. - วิทยาศาสตร์และเทคโนโลยี
![Yoshi Rinrada - 'มาทำไม' [Official MV]](http://i.ytimg.com/vi/r41xbfRLkLs/mqdefault.jpg)
watch at 1.5x speed :)
btw great video!
Thanks! I tried to make it so everyone could understand. The speed up option is there. I think I have naturally started to present quicker now though.
Great suggestion! Going to do that :D
@@StudyStreamPlusIt is okay bro. Slow pace gives beginners some time to digest while listening!
Amazing. One of the greatest videos I have seen regarding Git branching. Elegant but simple.
Wow, thank you! Please consider subscribing for more!
Thank you very much, you have explained it simply and yet effectively.. covering the core concepts.. appreciate your efforts!
Thanks so much! Please consider subscribing for more! 😀
Extremely informative. Thank you.
No worries. Please subscribe for more content! 😀
Great starting point for people Rev.
+MattBullsVideos Thanks Matt.
Thank you very much! , I will use this approach in my team
Great! Happy to help.
Thank you very much for your effort, you helped me a lot!
Ah no problem. Glad to help!
Thanks Reval. Great explanation!
No problem. I am happy it helped you!
Well done, thanks for the effort!
Thanks so much. Please consider subscribing for more. 😀
Dude... You are awesome.
+sagar podilapu Thanks Sagar! I hope the video helped out a lot.
Very clear and comprehensible. Thank you!
Glad you liked it! Please subscribe for more. We are working full time on the channel now.
Thank you.
It was very useful.
No worries. I am very happy you found this video useful! Please subscribe for more informative videos. Have a nice day!
UPDATE
Scenario: You need to make a "hotfix", after you have already created a "release branch".
Solution:
1. You should create your "hotfix" branch as described at: 10:52
2. Once you have completed your "hotfix", you should merge it back into "develop" and "master", as described in the video.
3. You also need to merge your "hotfix" branch into your "release" branch. This is to ensure your release branch has the latest stable code.
your channel is awesome. i was looking for such a channel for years. thank you.
Wow thanks! I am happy my vids help you. I appreciate the support. Please subscribe to get notified when I upload a video and tell you dev friends. Have a good day!
you got that
Thank you, Reval. Very informative.
Glad it was helpful! Please consider subscribing for more! 😀
Nice video. Now I have a basic understanding about git flow. Thanks.
Awesome. Please consider subscribing for more. 😀
thank you from Switzerland!
Glad it helped! Please consider subscribing for more. 😀
Thank you. Very well explained.
+kartik narayana maringanti No problem
+kartik narayana maringanti No problem
Excellent, one of the best explanations.
Thank you very much. Did you watch Part 2?
Thank you! It's very clear for me. Nice diction for non-english user.
+Виталий Волович Great. Happy to hear it helps.
+Виталий Волович Great. Happy to hear it helps.
Really great video pal, but indeed.. the speed button was very useful here! Keep up
Thanks! Yes, my delivery is slow on purpose here. I thought people would just use the speed up feature of the player like you. However I have changed my style to be faster.
My understanding was that hotfixes were more generally more severe bugs that require immediate attention since it is a "hot" issue.
Thanks for sharing Reval! Cool webpage btw :)
Thanks so much.
awesome explanation even anew guy can also easily understood...
I read the article which you linked about the git-flow process, in that hotfix branch scenario will in critical bug case but you told in the video as minor changes. so, please give me clarification that which one is the correct scenario of a hotfix?
once again thank you for your great explanation..
thanks for this good explanation.
You are welcome! Please consider subscribing for more! 😀
great effort, thanks
No problem. Glad it helped you.
Thank you so much
No problem. I am happy to help.
Deserves a like
Thanks! Please consider subscribing for more! 😀
How should we do if we have parallel feature branches, for eg. Feature A and Feature B, but they will not release together to Live? In that case, may I know how should I merge into release branch?
a feature is merge with developer if its totally done not otherwise. for you question, dont event push a feature branch to developer if you dont want it to be released or go live.
Mate, your git flow chart is incomplete, I think you are missing the bugfix/hotfix branches. You have to create a bugfix/hotfix branch from the release branch (if there is a bug in the release branch). when you are done with the bugfix/hotfix, merge it back to release branch, after that you can merge to master and develop branch.
well done
Thanks.
good training video, well delivered, shame about the audio quality (strange booming echo).
Thanks!
No problem! Please consider subscribing!
Simple and clear! Thanks a lot. Is it able to download the slides?
Sorry, unfortunately not. We don't have the slides for this anymore. Please consider subscribing for more content though! 😀
@@StudyStreamPlus Sure. Thank you very much!
I sub, thanks!
Cool. I really appreciate it. Hope you are enjoying the new content.
just a minor thing, with this flow, hotfixes doesn't make it to release/uat environment, which can sometimes be an issue.
I think this is a good point, however it depends on how flexible your infrastructure and deployment process it.
Great video thanks, watched at 1.25x
Thanks, yes I was slow on purpose. Please use the speed up feature if necessary.
Nice 👌
Thank you! Cheers!
Good Jobs
Thanks so much. Please consider subscribing for more! 😀
What is release flow
super..
Happy to help!
1. Download the 'video speed controller' browser plugin
2. Increase video speed to 1.50
3. ???
4. Profit
You can increase the speed using TH-cam's player.
increase speed by 2x
Hi there. Thanks for the feedback. We will keep this in mind for future videos.
If you find the video is too slow, please consider using the playback speed setting. You can find this in the settings cog icon on the TH-cam player to increase or decrease the speed. This should help.
So basically, an SVN
Not really. It is a model/methodology to apply to working with version control.
gotta couple of suggestions (might as well stop reading now) dont put text that ure reading already on the screen. while talking emphasize or just goddamn open sourcetree and show what ure talking about. get ur mic closer to you. or just fiddle with the settings. but please, slides are not for putting the same text you re reading. never ever do that. dont let your teachers do that. dont do that in the exams. dont do that in a meeting. dont do that on youtube.
rofl at how slow you talk
Yeah it was my first video. I thought it would be best to talk slow. If people preferred it quicker, they could just the TH-cam player speed up feature.
I only made it to page 1, "git flow" is the name of a git branching model published by Vincent Driessen on his website nvie.com. Of course you can choose to follow it, or pick any other git branching model, but if git flow is mandatory, these are hard rules, not guidelines.
And you speak way too slow for my personal taste.
Can you move the microphone closer to your mouth and speak up, this video too quiet and sounds like it was made in a library.
Hi there. Thanks for the feedback. Our latest videos have improved dramatically in production value and still contain great information. Please consider subscribing for more. 😀