Master(main branch for), feature branch for added functionality. Release branch for delivery to customer, instead of building application from master we build and deliver to customer from release branch. Master branch is for active development. Master branch can be for testing.

This channel is Gem for Devops mastering, I appreciate your efforts, Good work!!!

Abhishek Sir, we are on our way please keep making videos don't lose motivation in future this playlist will be one of the best tutorial on KZfaq trust me.

It's truly fantastic to have the opportunity to learn the DevOps course with real-world examples, which are often not offered by other institutions. Thanks Abhishek 😊

My vocabulary is not enough to Praise You....Thank you so much sir

Thank you so much sir you are doing really great thing. Outside other institute charge for devops to learn many of the students who want to learn devops they are not able to learn devops because they can't afford fees that much but you are teaching free so that they can learn really it's great thing sir. Thank you so much once again.

hi sir, thanks for your time to guide us! This what i understand. The default branch we call it as master branch. under the master branch will be another 2 sub-branches 1.development branch and 2. release branch. 1. development branch --> we create an feature branches as per the devlopers team size. 2. release branch --> through this branch will release to production. if bugs in prod. will create the hot-fix branch under the release branch. Thanks.

Abhishek sir, you can also put contribution for your effort. We can contribute some amount for you. It's for our satisfaction. If anyone wants to contribute, they will do. Because every institute will charge a lot of money. But you are teaching without fee.

Super brother your explanation and your example, already i referred your channel to my friends keep it up thank you for providing this much of knowledge to us with free of cost 👏👏🙏🙏🙏🙏🙏🙏

Beautiful Explanation 👍👍👍👍👍

Great Uber example, Explained well.

Date- 21/08/2024 , Completed the video . FOund this a bit tough. Hopefully doubts will be cleared in upcoming videos. Thank you.

Hi Abhishek veeramalla I had just started exploring your playlist, you are simply an amazing mentor

Completed day -10 successfully

Completed Day:10 Video and Practice also done. Thanks Veeramalla garu GK from NJ

Content was really good 👍

Learned something new about Git which I was unaware of until today.

I understood branching strategy clearly thanq so much abhishek for you your efforts to make understand the concept of branching

Hi Abhishek excellent session. Thanks for brushing up my git knowledge.

Thank you so much abhishek ...actually now I came to know about your channel but it was really good and very simple way to understand your all concepts definetely i m going to watch all devops videos ,u are done great job thank you so much again lots of gratitude🌸

You are God of devops sir

Thank you so much for this video, got my concepts cleared related to branching strategy

Thanks a lot. your doing great job . I appreciate your efforts , I tell you bottom of my heart.👍👍

Wonderful explanation!! Truly thankful 👏

Thank you so much abhi sir, got the complete understanding of the concept. Completed this Video on 29th June 2023.

Great explanation Sir.

🙏🙏🙏❤ for ur dedication and teaching

Very nice explanation Abhishek bro....Keep on rocking the knowledge sharing...my lovly kudos to u

Thank you so much. The explanation is fantastic and helpful. You are gonna be my mentor..

Awesome content, keep it up Abhishek...Love and respect from Pakistan.

Awesome. Got this topic so easy. Thank you Abhishek ❤

Thank you Abhishek 🙏

awsome

Day-10 Completed successfully :) and Thank you Abhishek :) .

Super anna....Neet ga explain chesaru.

Thanks Bhai! Go On.

Thanks Abhi.. Clearly understood 😊

Thanks so much sir you’re doing a wonderful job

Thank you Abhishek, it's very clear

Thanks a lot. This is really good. I finally got it.

Thank You Sir! Learnt something new !

This is pure gold

Thanks a lot for making this video Sir. It was superb with real world examples ❤

Thank you Sir, I got the same question and explained exactly, though am working i didnt had this much idea,it is realy helpfull..

Superb, thank you

you r god of devops

Hello All viewers, Please dont mind to mention interview questions that you might have been asked ,These questions can help others.

so far the best video available on YT...thanks bro u r a savior...could u plz add or show how this branching strategy works in Jenkins as well?

Good explanation abhishek keep it up 👏👏

Thanks a lot. very well explained with examples.

Completed 10 days course.

great explanation .

Thanks ,its Clear concept.

Really love like video. It is easy to understand, and I now have some clarifications on some things I was confused about. God bless you for this effort

Thank you sir

Thankyou for the stuff but if you have showed practically that will help a lot more to the people....TQS bro

Grateful😇 Thankyou Abhishek

nice

Thank you bro, Very helpful.

Thanks

Hope that today it 'll be practical session of branching strategy.

Very Helpful!😍 Thank you So much

Great video :)

Awesome, got you. It's easy

I am watching from Noida Delhi ncr

Day-10 done ✅️🙂

Thanks for explaining the branching strategy. Could you please explain how this branching strategy to be used for deploying applications in various environment such as Dev, Test, production environment etc..

i completed this video abhishek

Well explained 😊 thanks

Abhi shek now iam thinking why i didnt find you one year back. Now i got to know your lectures one year back i took a course from intellipaat , those guys also not taught like this

Thank you for your presentation. How about the testing branch to validate new features before deliverying to customers?

Jai Balayya Jai Mallayya

Best

Great Explanation,Very easy to understand.How can we add tagging to release branches ?

Hi , great explanation? Are you planning to do any playlist for developers as a beginner?

Just a quick question - Release branch would most likely would have just commit that is common to the master branch commit where one decides to branch for release. No further commits would go in Release branch from that point forward and new commits would go to dev branch (main/feature) and later on new release branch would be created when ready for release? Is my understanding correct? Thank you for these videos Abhishek.

thaank you 💐

Thank you ^^

Good content brother, it will be very helpful if you privide notes{your content and interview question and answers} also .

Hi Abhi It was a greatest stuff I could say. And I would like to thanks a lot. Are you sure this course will definitely will add a clear demo of What's involved in DevOps. I would like to thank you a lot for you initiative to support many for free.

Hi Ahbishek, It was really amazing if you had chance to do video on complete real time pipeline using groovy to deploy in qa uat prod with the help of jenkins shared library so that i t would be very useful to crack any devops interview

hi bro if possible can you please do Realtime hands-on videos so its help full to us

Thanks 🙏 so much. But I have one doubt to clear, how would you compare main, dev, staging and uat branches to main and releases branches covered in this video? Keeping in mind that feature and hotfix branches are common to both? Thanks once again. You are a healing to many

@abhishek : Is this called Git flow strategy which you have explained Pls clear my doubt… Btw it was great explanation thank youu

sir can you please explain the difference between trunk based and gitflow branching stratergies

It’s very clear and perfect explanation thanks abhishek I have one small concern so the organization when ever a product is ready for a customer phase they create a release branch and they go ahead for release and then they keep updating the master branch whenever they are ready with other version again they create release branch and then host it so that they can continue testing and do improvements on master branch.. so according to this video there might be more than one release branches right ? This is what I understood if I am wrong please correct me !!! I will be waiting for your response Thanks in advance!!!!

Thanks once again Abhishek, could you suggest which is the bes strategy ? i heard names like Git flow strategy /Git hub flow strategy/ features branching strategy? We discussed about Git flow strategy in our video am I right?

Abhishek,could you just show a practicals on merge and rebase.

great seesion, thank you. I have one query - In github should we need to create hotfix branch from release branch or master branch?

Hey, Abhishek, very helpful videos and nice clear explanation on GIT branching strategy. I used to work as Front-end developer mainly when pushing codes, I used to face problem like let's say Dev 1 is working on feature "xyz" and Dev 2 is working on another feature but dev2 is dependent on Dev 1 feature does Dev 2 needs to wait until Dev1 finishes developing feature? Or dev 2 can go head and create separate branch / same branch as Dev1? and start working on developing feature Dev2 pull code after Dev1 finishes and everything has been pushed faces lot of Merge conflicts? how to avoid Merge conflicts? any Git commands to check before avoiding merge conflicts?

Hi Thanks for the detailed video , If we get an issue in production shortly after a release, you mentioned we can create a hot fix branch and release that branch on to prod. Any downside if use same release branch which was used for actul release instead of creating a new branch ? assuming we use hot fix branch , what's the order of commits to give the fix, would developers make commits first in hot fix baranch or master or release ? what's the source branch for Hot fix branch ?

Hi Abhishek, thanks for the sessions.. in the previous videos u told abt the github test repo. while practising, i found some other options in GIT.. desktop app o GIT.. how is it diff. can we use the desktop app as well.. please make me understand. TIA😊

❤

First Comment

I thought master/main is a production branch for customers, but now I understand it just updated code maintaining branch, Release branch is the production branch for customers. Am I correct? By the way Thanks for wonderful series, I will complete the entire series soon❤

Hi Sir, Just one query How this branches works in different different environment, ? like Dev,QA,Pre-prod,Prod ?? which branch goes where ? & how deployment will happen..please help on it..

Hello Sir! waiting for Day11

Hello, Thanks for the great video. I would like to know new versions are only deployed from Release Branches? Main branch is not used for deployment? Is main branch only for maintaining all codes of versions?

you meant multi branching for microservices application according to your explanations. Right?

Hi Abhishek, how can specific people merge their changes directly to the master branch rather than raising pull request. This was the question asked in the interview. Could you please answer this.