Understanding Git for CICD - Biggest Mistake I made

Описание

If you're like me, you probably find git very confusing. This makes learning about stuff like CI/CD challenging because git is core to these workflows.

My big problem was using git incorrectly and not realizing it. I committed changes directly to my main branch.

This leads to scenarios that Dr. Brown warns about in Back to the Future. You make changes and the next thing you know, Biff is a millionaire and married to your mom. While you can revert, drama ensues. Good for movie fans but bad for you.

There are many alternative paths, but one popular pattern involves creating parallel timelines (or branches) for your specific change, i.e., go from 1985 to 2015 to prevent your son from going to jail. Rather than make changes on the main timeline, we make changes in that alternate reality branch.

This doesn't prevent bad things from occurring, but it at least provides an opportunity to check if Biff has become a gambling kingpin and Hill Valley a giant biker bar. If so, don't merge that code. Bad for a movie plot, but good for you.

We can check for these bad outcomes manually, or we can do it automatically each time someone asks us to merge their parallel universe into our main timeline (hence the ""Continuous"" thing)

This video I walk through two paths:
- Bad: make changes and push to main branch
- Better: create a new feature branch, make changes, and open a pull request. This opens up the world of CI/CD.

If you've used git but never really felt comfortable, this is for you.

And Continual, we're helping #ML teams use software engineering best practices. This always means some sort of #git-based workflow, among other things

Hit me up or connect with me on LI: https://www.linkedin.com/in/gustafrcavanaugh/