Git for Teams: Streamlining the Fetch, Pull, and Merge Process

[@Jeff24Y]

Thank you! This is amazing. Please continue giving practical examples!

[@omkarhalankar1729]

Very helpful and with the clarity of the real life scenarios it really boosts knowledge!

[@alexandreneo888]

Simple and clear explanation!

[@ppcuser100]

One of the best explanation 👌

[@aldairandre]

Thank u, u saved my life bro!

[@akodev]

Happy to help

[@srinivasqa2021]

when i did a git fetch -all....i didnt get the list of branches what actual it is

[@snowman6000]

Awesome thanks for the info!

[@atherk4824]

Hi Ako, We are using git for Power BI Dev. Similar scenario. If I and my team mate clone a repo copy and start working the same time on different files of the dev work and say my co worker finished his work before me and deploys the dev work file to the main. and I am still working on mine and am ready to deploy a day later. would i just commit and push and my file will merge into main or should i do a pull and merge as you did to incorporate my changes into the main?

[@akodev]

After your coworker pushes to main, make sure to Add, Commit your work, then Pull. if you dont add and commit you can overwrite some of your work. after you pull, you can push or keep working. but pulling will update your local version to be on par with whats happening on master.

[@atherk4824]

@@akodev Thanks

[@KoJIJoky]

TY

[@justincaseOne]

that was good