GIT Branching Strategy for Enterprise project | what worked for me 

i will explain those when I get time. yes when deal with 100+ engineers commits having prior review from a TL is helps architects as then they don’t need to deal with minor oblivious issues

thank you sharing the idea. will do an other video regarding feature rolleouts

@@krish I see lots of devs misunderstand CI/CD. CI is not entirely your build pipeline. CI is when everyone's code get merged into master/main (trunk) branch hence the term in integration. It's is recommended to merge the feature branch at least per day, hence the term continuous. so what's happen when developer code is not ready, that's ok you disable the feature and continue to merged the code master. Next come CD, so your feature disabled/enabled code continuously release to other environment. when you are ready you can simply enabled the feature. Next level is progressive delivery, you can enable the feature visible to 30% user and the measure the error rate. if no error you increase it to 50% and so on. Continuous is faster than people think here. This the modern DevOps practice. When you have separate log living branch you are doing continuous isolation(think about the time you have to spent to review code for each of these branch merges), you have build more than once. When you do Trunk Based Development you build once and deploy anywhere. When you do continuous integration and deployment this way you don't need release schedules.

Personally I keep feature branch until its next version release to production. ex: 5.1.x feature branch stays till 5.2.x release to prod. but its personal choice. in trunk based development you can delete branches without an issue

@@krish Thanks sir.

Thank you for sharing. yes this almost same. but better keep a tag for every release as that making sure we have "copy of the production code"

​@@krish Yes sir, we need to have a tag for every release. If something needs to go immediately, then the best way is to create a branch on the release tag and deploy it to production from there. I am a big fan of your work and really appreciate your series on microservices.

same. create new release branch along with previous release deploys and put the commit to that. BTW what sort of usecase for daily releases? how do you manage QA / UAT sign off?

@@krishthat why I wanted how do we deal with this situation. Imagine the the use case of stock market related or zerodha kite goes every day updates in the night with release.

i did not delete comments. you can see many negative feedback comments on videos. i didn’t delete those

i just checked. i can see your comment in this video and also I have replied to it. why you say its deleted?