The gitflow workflow - in less than 5 mins.

Great tutorial

Credit for the music? Lovely track :)

Thanks much! That's a quiet simple and to-the-point explanation.

your second name is god, you don't know but it is.

Thank you!! So glad I found your beautiful and simple explanation! and this calming soundtrack!

Thank you man, you make me have any idea of how works git workflow in less of 3 minutes.

awesome tutorial but what...a....nightmare

What if Feature 1 is merged back to Develop branch, and also Feature 2 is merged back to Develop. But only Feature 2 is going to be released to Production? How are you going to remove Feature 1?

That line from develop branch to feature branch giving me anxity 😵‍💫

Awesome explanation! Thanks!

Thank you for the easy example 😎😎

Very easier explanation within 5 minutes you nailed it, appreciated keep it up.

This is so perfect....wow..thanks for explaining it like this!!! God bless you!!

Best explanation ever

thank you , Sir ! very easy to understand

like!

You need to branch out from master only for hotfix release

Awesome video. Just answered all the questions I had in just less than 3 mins.

This is very useful , thanks :D

Thank you.. this video can explain better than others

This is so clean. Thanks!

one hit wonder

nice and fastest one

I got this video referred to me by some org. Well done. awesome information,

Great vid!

awesome drawing awesome explanation. awesome video

It was useful. Thank you.

Great video

Thank you 😊❤️

This 5 mins video was better than many 15 mins videos I watched. all my questions were answered without a single word being spoken! 👍

Concise and straight to the point. Nice.

Very well done! I wish you would have created more videos. But, if you are going to create just one, it might as well be perfection.

not good for continuous integration and if you have multiple environments such as dev, test, prod.

Fantastic video - thank you for this. I've been looking for exactly this for the past 5 years. It's the perfect illustration. Much appreciated. Would love to see more :)

Anybody can say, from which branches the tester or QA will test ?

Excelent! 2 mins!

...exactly what i needed! i feel like Neo in The Matrix lol <3

i dont think so is a good idea merge back to feature branch, it must be deleted after merge in develop

Best video on GIT FLOW..You explained everything without saying a word in less than 3minutes..Kudosss..You just nailed it

Hello, thanks for the video! It was very well done. For the next part can you do a video about how to accomplish each step with Git commands? I'm a little lost on how to integrate a branch into two others. Thanks!

One of the best video on Gitflow! Thanks much for sharing!
Can you explain how many test environments are needed for testing these features/HFs/releases etc? Looks like we need many. Please explain.

hi, devchild, thanks for such nice video for git. Can you tell me which tool have you used to create such animation in this video?

I know this concepts are confused, but if you can organize you team, believe me, you will get an step up.

anybody who knows deeper understanding can summarize it best. this is it.

works fine on paper but on practice gitflow has been shit.
NO CODE AWARENESS. if you are working a simplefeature on new files then good. but if you are working on adding new features to a bunch of old files then goodluck, coworkers who are working on another feature branch have no idea what the fuck is going in your own branch. and by the time you merge,

BOOM tons of conflicts, duplicate functions and css that do the same thing.
you wait a huge work that you are about to merge??? ha! too bad someone renamed that file.
trying to merge a bunch of ifelse blocks? oops, looks like someone refactored a the function that you were trying to patch.
feature1 make element1 visible on small devices, feature2 element1 is refactored into a different component. GOOD LUCK.

thanks! i cried

What tools/apps did you use to draw these nice plots?

First time watching a release management video with zero anxiety

Wow Short & Sweet clear explanation

I've been using this for 3 year in my previous company, unfortunately I left, and now Im in a new company and we're just 2 developers. Unfortunately, my colleague doesnt agree to this design, how can I convince? The fear is on develop branch getting messy and git might produce bugs and delete codes, I dont know how to argue with him because he has 10 years experience and I just have 6,
right now, we keep on rebasing our feature branch against master. It looks clean but if the PR are getting too many, it's kind of a hassle to rebase them everytime a new merge is done. so frustrating.