For example, a file “remembers” when it was created, so if you move that file into another directory, its creation time remains the same.īlobs, on the other hand, are just contents - binary streams of data. The difference between blobs and files is that files also contain meta-data. In git, the contents of files are stored in objects called blobs, binary large objects. These directories contain other directories, and/or files (for example, /usr/1.txt). It is very useful to think about git as maintaining a file system, and specifically - snapshots of that system in time.Ī file system begins with a root directory (in UNIX-based systems, /), which usually contains other directories (for example, /usr or /bin). Are you up for it? 😎 Git Objects - blob, tree and commit We will also create new branches, switch branches, and create additional commits - all without using git branch or git checkout.īy the end of this post, you will feel like you understand git. This will allow us to deepen our understanding of what is happening under the hood when we work with git. Next, will create a repository from scratch - without using git init, git add, or git commit. We will dive into the working directory, staging area and repository.Īnd we will make sure we understand how these terms relate to the git commands we know and use to create a new repository. We will then briefly discuss branches and how they are implemented. We will start by covering objects - blobs, trees, and commits. We will get a rare understanding of what goes on under the hood of what we do almost daily.
#Does git checkout readwrite series#
I also uploaded a YouTube series covering this post - you are welcome to watch it here. Still, we will start with an overview to make sure we are on the same page regarding the mechanisms of git, and specifically, the terms used throughout this post. You’ll benefit from this post if you’re experienced enough with git to feel comfortable with commands such as git pull, git push, git add or git commit. īut even more acutely, I've found that understanding how git actually works is useful in many scenarios - whether it’s resolving merge conflicts, looking to conduct an interesting rebase, or even just when something goes slightly wrong.
But does it really matter?įirst, as professionals, we should strive to understand the tools we use, especially if we use them all the time - like git. Many people who use git don’t know the answers to the questions above. But how many of us know what goes on under the hood?įor example, what happens when we use git commit? What is stored between commits? Is it just a diff between the current and previous commit? If so, how is the diff encoded? Or is an entire snapshot of the repo stored each time? What really happens when we use git init ? init.shĬmake -DCMAKE_INSTALL_PREFIX=./install.
What should I add in my script file to checkout the code? I'm really tensed because I can't do it wrong once more.
What does he mean by checkout the code? I have done the other part of compiling and running the unit tests but they only work in root directory of the XYZ cloned repo.
I have only one chance at doing this and I can't do it wrong or ask him. I know that git checkout means to go to another branch but I'm not sure whether I should git clone the repo then git checkout -b new_branch or not
#Does git checkout readwrite code#
He will be running the code in a docker container. His exact words are these : Write a shell script that will checkout the 'XYZ' code, compile it and run the unit tests. One of my professors told me to write a shell script that checkout code.
0 kommentar(er)
