What is Version Control in Data?

Free AI web copilot to create summaries, insights and extended knowledge, download it at here

918

Abstract

/b>” and that is managed. This is where the likes of major GIT providers such as GITHUB, GITLAB, BITBUCKET, AZURE DEVOPS fulfill this purpose.After you have come back from your lovely coffee break, you realize your colleague, wants to borrow the introduction you wrote, now what?They can create a branch off your work, creating a new section of the work in their part of the book shelf, and start working there.Now the fun part comes, you added a little more text, and your colleague has also done their part, now lets combine these 2 sections. This is called a merge branch/request. Where we work together and look at combining the respective pages of our articles together and submitting them into the always backed up cloud library.Luckily today, another colleague has the afternoon off, and is ready to review the work on the

Options

articles, and give the review and go/no-go. This reviewer, is a critical person in this process, as they control the quality of the work and conformance to standards. Call them the gate-keeper if need be.After the green light it given, the merged changes are added back to the cloud library, where the article is safely stored and retrievable.You might have picked up this is a super simplistic way of explaining version control.If you liked this content, please subscribe and give me your feedback😊<figure id="a9ce"><img src="https://cdn-images-1.readmedium.com/v2/resize:fit:800/0*9mKTMCpIFHPeqAvw"><figcaption>Photo by <a href="https://unsplash.com/@mzakatiura?utm_source=medium&utm_medium=referral">Mariia Zakatiura</a> on <a href="https://unsplash.com?utm_source=medium&utm_medium=referral">Unsplash</a></figcaption></figure></article></body>

Beginners guide

A few people have asked me what it is version control in data and why is it important?

Well, I will break this down to layman terms and analogy, do ask any questions you have! 🙌

Well take it as your work is involved in writing blogs and books, and what is one thing you need to always make sure you do. If you are like me, I’m OCD on Ctrl+S → saving! — I don’t want to lose my work!

Let us say, you need to go for a coffee break and need to keep the article somewhere safe and backed up.

You will need to create a section, or I call it a branch. This branch has the goodies and your hard work. You will want add your work to this section, and store it in the library. Nowadays, we all want things to be backed up to “cloud” and that is managed. This is where the likes of major GIT providers such as GITHUB, GITLAB, BITBUCKET, AZURE DEVOPS fulfill this purpose.

After you have come back from your lovely coffee break, you realize your colleague, wants to borrow the introduction you wrote, now what?

They can create a branch off your work, creating a new section of the work in their part of the book shelf, and start working there.

Now the fun part comes, you added a little more text, and your colleague has also done their part, now lets combine these 2 sections. This is called a merge branch/request. Where we work together and look at combining the respective pages of our articles together and submitting them into the always backed up cloud library.

Luckily today, another colleague has the afternoon off, and is ready to review the work on the articles, and give the review and go/no-go. This reviewer, is a critical person in this process, as they control the quality of the work and conformance to standards. Call them the gate-keeper if need be.

After the green light it given, the merged changes are added back to the cloud library, where the article is safely stored and retrievable.

You might have picked up this is a super simplistic way of explaining version control.

If you liked this content, please subscribe and give me your feedback😊