GIT 3 Branching Strategy | Github and GitLab Branching Strategy | Must know for all engineers

GIT 3 Branching Strategy | Github and GitLab Branching Strategy | Must know for all engineers

22,035 Просмотров

Ссылки и html тэги не поддерживаются


Комментарии:

@user-pc1pm1vb7p
@user-pc1pm1vb7p - 21.01.2024 08:13

how trunk based deployment strategy works then ?? can u please tell

Ответить
@alen740926
@alen740926 - 05.11.2023 07:49

thanks - when we create the hit fix branch out of master branch for production issue- where/ which environment are we testing the "hot fix" before pushing to production again? given Dev & lower environments has exsiting new features being tested?

Ответить
@heygokul
@heygokul - 31.10.2023 22:28

Well explained. Thanks!

Ответить
@nishantvishwanadha2912
@nishantvishwanadha2912 - 27.09.2023 08:53

Thanks a lot for detail and pictorial explantion

Ответить
@theSDE2
@theSDE2 - 22.08.2023 18:43

This is awesome. Shreyansh can you teach us what is the ideal way to do a bug bash in the team for our application or just for the Backend.

Ответить
@nikrajput3512
@nikrajput3512 - 10.07.2023 10:00

Hey Shrayansh ,You had told that you won't make other than Interview questions as private .But you made one of the most important topic : Concurrency Handling as Members only .This is not fair yaar

Ответить
@motivation_hubPJ
@motivation_hubPJ - 09.07.2023 07:46

Thanks a lot for the video . In our org we don't keep release and master separate . Mine is not MNC though. But i feel there are certain advantages for the same. First in case multiple teams are deploying in prod in same day then it becomes difficult to monitor to separate release version on prod. Second in our org we have restrictions on which branch can be deployed in prod . We can only deploy master in prod. This helps to maintain consistency . Also it becomes easier to find out what is the diff btw code in prod and qa envs. Lastly on the point of hot fix. we do have a lot of hotfixes but usually we don't face problems with same because any hotfix will be merged via pr and the code diff will always show the changes. Not sure if this is a correct way but is working for know. Please let me know your pov on this or why it may not be a approach . Also Shreyansh if possible can we have a community channel of discord /slack . Have a lot to discuss with you 😅. Thanks again for all your informative video.

Ответить
@AshishGusain17
@AshishGusain17 - 09.07.2023 07:14

Hi Shrayansh..thnx for the video.
Query: Is the only use case of master branch is when we get a bug in prod and regression testing is going on in release branch?

Ответить
@yuvhrajverma9665
@yuvhrajverma9665 - 07.07.2023 17:35

Sir till when are u planning to complete ur system design course, it would be really helpful if u complete it early

Ответить
@vishalghanghav748
@vishalghanghav748 - 07.07.2023 08:43

Interview on Monday .Concurrency ka video aa jaaye to maja aa jayega

Ответить
@anilsahu5709
@anilsahu5709 - 07.07.2023 08:07

Hotfix back merge to Release might impact regression

Ответить
@prasenjitsutradhar3368
@prasenjitsutradhar3368 - 07.07.2023 07:16

Looking for Branching Strategy for a long time......thanks a lot!

Ответить