Committing Atomic Changes

Question 1

What is version control?

Answer 1

Version control or source code management tools or revision control system take on the task of keeping a software system consisting of many versions and configurations well organized. Version control tracks every iteration of your product or application, basically a log of your history and versions of software.

Question 2

How to install git?

Answer 2

1. ) To install git simply run $ sudo dnf install git-all.
2. ) Set the username to identify your repository $ gitconfig - -global user.mail myemailaddress@aol.com
3. ) You may want to set the editor you’ll be working in $ git config - -global core.editor “subl” -w
4. ) You may want to set some coloe to your interface. Run $ git config - -global color.ui true.

Question 3

If git is installed how would you go about creating a new repository on your computer?

Answer 3

Create a new folder and inside the folder run $ git init.

Question 4

Inside every repo you create there’s an invisible .git folder that’s developed. What kind of files might you see if you opened that .git folder?

Answer 4

You should see HEAD, config, hooks, objects, branches, description, info, refs. Each file is critical to know and be familiar with if you want to master git.

Question 5

Most version control systems have 2 tree architectures: a working directory and a repository. What about Git?

Answer 5

Git has a 3 tree architecture: working directory, staging index, repository. Think of the workking directory as the work on your local computer.

Question 6

When you go through with a commit one of the major things the computer does with your commit is to assign what to your commit?

Answer 6

Git gives that commit a checksum #. The top of your commit chain will always have a HEAD pointer indicating the most recent commit or a pointer to the current branch reference. This reference later becomes a pointer to the proceeding/new branch.

Question 7

What command would you run to see your commit history?

Answer 7

$ git log

Question 8

What command would you run to show the difference between the last commit and a recent commit?

Answer 8

$ git diff

Question 9

What would $ git diff - -staged do?

Answer 9

git diff - -staged will show you only the changes made to the files in the staging index.

Question 10

What command do you use to remove a file from your repo?

Answer 10

$ git rm file.txt

Question 11

How do you rename a file in your repository?

Answer 11

$ git mv firstName.txt newName.txt

Question 12

How would you go about undoing changes on a branch after you’ve just written new code and want to revert back to the old code?

Answer 12

$ git checkout. This pulls your latest commit and ignores any changes you have in your working directory.

$ git checkout would pull your branch and allow you to start working on it.

Question 13

How do you unstage things?

Answer 13

$ git reset or $ git reset HEAD ( both of these reset staging to the last commit ), just after you add a file to the staging index, if you added the file already reset would not work.

Question 14

How to amend your last commit message?

Answer 14

https://www.atlassian.com/git/tutorials/rewriting-history

$ git commit ammend -m “this is an updated commit”

Question 15

How do you define a git alias?

Answer 15

$ git config - -global alias. ;
$ git config - -global alias.unstage ‘reset HEAD –’
$ git config - -global alias.civ ‘commit -v’;
$ git config - -global alias.ci commit
$ git config - -global alias.st status;

Question 16

How would you use git add

Answer 16

https://git-scm.com/docs/git-add

git add is used to start the process of updating your project version. You might say git add . (all), or git add -p, or git add -A (all), git add - -all (you guessed it!).

git add patch is a way for us to select chunks of changes we want added to our index one at a time rather than all at once.

Question 17

What does git checkout - -patch do?

Answer 17

git checkout - -patch
git checkout -p

We know git checkout helps us switch branches but if we run git checkout -p we do NOT switch branches, instead we update the named paths in the working tree with files from a tree-ish or a particular commit/tree.

Question 18

Explain the differences between the git HEAD, work tree and Index! Also what is the local repo and remote repo?

Answer 18

https://stackoverflow.com/questions/3689838/difference-between-head-working-tree-index-in-git

• > The working tree is the work on your computer.
• > The index represents a staging area or checkpoint of sorts.
• > The local repo is the repository we commit our messages to and if your local repo is master it is master.
• > The remote repo is a repo which exists on a different computer, it could be the master repo and it might not be. If you had changes on your local repo you might either push it to master or have someone merge it to the master repo.